PyCLI, WUI, API upgrades #291

…ed development mode to menu container bootstrap

… there wasn't an issue

…ervices: adminer: grafana, dashmachine and gitea

…con handling locally. Added buttons to build history

…ders on CLI

…k dropdown selection

Upgraded menu to use an API. Created a Web UI

…ested hiemdall and portainer

…l services

… protocol

Wui/api updates for experimental

…on PyCLI menu

Wui

@Paraphraser

…2 (thanks @Paraphraser)

…on cli

Changes pin from 1.8.4 to 1.8. This will pick up the multiple images tagged with 1.8.5 (following on from multiple images tagged 1.8.4) and any future 1.8.6 etc. Formatted as per your Discord advice (1.8, 1.8.4, latest). The problem I see with "latest" is that it doesn't work.

Removes 9981:8080 port mapping (unnecessary).

Pin InfluxDB to 1.8 - PR 3 of 3 - experimental branch

Octoprint - ports - PR 3 of 3 - experimental branch

Implements consistent service definition across all three branches. Documentation consolidated into master branch. Includes step-by-step guide to proper initialisation. Documentation in old-menu branch reduced to a stub pointing to master branch.

Uses a consistent service definition across all three branches. Removes commented out capabilities which seem unnecessary. These seem to have been inherited from old-menu. Not present in master branch. Fixes typo in `EXTRA_JAVA_OPTS` environment variables (no leading quote mark). Also switches default time-zone to Etc/UTC. Copy of documentation from master branch.

Nextcloud - consistent service definition - experimental - 3 of 3

1. Fixes egregious formatting error in EXTRA_JAVA_OPTS. My bad! 2. Sets default Java timezone to Etc/UTC. 3. Leaves logging options unchanged (ie as I found it).

openHAB - consistency fixes - experimental branch - 3 of 3

Adds service definition from [IOTstack tutorial: Quick and Dirty WireGuard](https://gist.github.com/Paraphraser/f46014b8a27e3f878f07657d6db4490e) gist, with two differences. Instead of hard-coding the following environment variables: ``` - SERVERURL=your.dynamic.dns.name - SERVERPORT=51820 ``` this PR follows the convention of using the `Unset` key: ``` - SERVERURL=Unset - SERVERPORT=Unset ``` Adds same `duck.sh` proposed in PR 1 of 3 in this PR group. No changes to documentation. I'm assuming there will be appropriate consolidation and rewriting of documentation as `experimental` approaches mainstream.

1. Adds Dockerfile to MariaDB template to add stability patches recommended in: * [StackOverflow](https://stackoverflow.com/questions/61809270/how-to-discover-why-mariadb-crashes) * [Discord](https://discord.com/channels/638610460567928832/638610461109256194/825049573520965703) Note: * I have been running these patches for three months and they definitely improve stability (zero crashes in nextcloud_db). The Discord link above contains a similar stability report for MariaDB. 2. Alters service definitions for both MariaDB and Nextcloud to: * build using the Dockerfile * add a volume mapping to support backup/restore of MariaDB database. Note: * it was a conscious decision to place the db_backup folder in `./volumes/CONTAINER` rather than mimic the arrangement for influxdb. It simplifies the backup/restore design. 3. Adds port mapping 9322:3306 to nextcloud_db service definition. This is needed so "restore" routines can tell when the MariaDB service is open for business. Note: * MariaDB already exposes 3306:3306.

1. Implements self-repair functionality by adding `Dockerfile` and `entrypoint.sh` to the Telegraf template. 2. Removes `telegraf.conf` from Telegraf template. The default configuration file is now the one supplied with the container downloaded from DockerHub. In other words, it will always be kept up-to-date by the container's maintainers. 3. Alters service definition to: * use a persistent storage area in `./volumes/telegraf` * remove the old `./services/telegraf/telegraf.conf` file mapping * add explicit mappings for all exposed ports. Note: * I made no attempt to follow-up with changes to either `build.js` or `config.js`.

Adds Chronograf and Kapacitor service definitions to complement Telegraf and InfluxDB, and complete the TICK stack. Assumes Chronograf may be added without Kapacitor (uncommenting relevant lines in Chronograf service definition is required to enable full integration). I made no attempt to create matching `build.js` and/or `config.js` scripts.

Note - `build.js` references `wg0.conf` and `services` directory structures but I have not attempted to fix it. All IOTstack-side setup for WireGuard is completely unnecessary. Wireguard is a well-behaved container that handles its own initialisation properly with no help needed from us.

20210702 WireGuard - experimental branch - PR 3 of 3

…xperimental 20210809 MariaDB + Nextcloud - experimental branch - PR 3 of 3

20210823 Telegraf - experimental branch - PR 3 of 3

20210826 TICK - experimental branch - PR 3 of 3

A problem affecting the build of the Mosquitto container keeps showing up in Discord questions. Examples: * [2021-09-17](https://discord.com/channels/638610460567928832/638610461109256194/888096248761045022) * [2021-09-09](https://discord.com/channels/638610460567928832/638610461109256194/885494986710335498) The problem is discussed in [alpinelinux/docker-alpine issues/98](alpinelinux/docker-alpine#98). It is not clear whether: 1. The problem is transient (ie those reporting it are able to get past the problem on a retry); 2. Only affects Mosquitto or potentially affects other Alpine-based IOTstack containers using `apk` to add packages (eg Node-RED); or 3. Environmental (eg if there is a proxy system between the Raspberry Pi and dl-cdn.alpinelinux.org). This Pull Request is implementing the patch suggested by Issue 98 of reverting `apk` requests to use HTTP. Given the march towards HTTPS-everywhere, reverting to HTTP might seem inadvisable but: * Issue 98 was opened in July 2020. * There seems to have been no significant progress towards its resolution since January 2021. * The Discord traffic suggests it is an ongoing and present issue for IOTstack users. Also harmonises Mosquitto Dockerfile on experimental branch with the common versions on master and old-menu branches.

@wijnsema

In [Issue 289](#289), @wijnsema proposed removal of Portainer. There has been additional support for this from @mats-nk. It is coming up to a year since Portainer-CE was added to IOTstack so this PR is my way of saying that I agree with the idea. 1. Remove Portainer service definition. 2. Remove Portainer documentation. 3. Copy Portainer-CE documentation from master branch.

`docker-entrypoint.sh` was out-of-sync with master and old-menu versions. `iotstack_defaults` directory missing.

Adds health-check script to template. Alters Dockerfile to import health-check script and adds `HEALTHCHECK` directive. All container documentation is in master branch.

Follows on from suggestion in [Issue 415](#415) to add health-check to more containers. See also [PR 406](dbb6217). Changes: * Adds `iotstack_healthcheck.sh` script to template. * Moves Dockerfile into `buildFiles` directory, and adds commands to copy the health-check script into the local image and activate health-checking on launch. Does not change any documentation on experimental branch.

A [Discord thread](https://discord.com/channels/638610460567928832/638610461109256194/891417109920362518) revealed several problems with Prometheus. This Pull Request makes the same changes as proposed for master and old-menu branches but makes no attempt to adjust `build.js`.

Changes `home_assistant` service definition to: * Reference ghcr.io containers, and provide options to select tailored images for Raspberry Pi 3 and 4. * Places container into Host Mode so it can receive multicast traffic. Documentation not changed (assumes master branch documentation is definitive).

Changes `telegraf` Dockerfile so that the configuration for sending metrics to InfluxDB uses the "internal network" URL: ``` http://influxdb:8086 ``` On a clean install, Telegraf should communicate with InfluxDB "out of the box". Acknowledgement: this problem was discovered by [Discord user "tablatronix"](https://discord.com/channels/638610460567928832/638610461109256194/898349626179076096)

@tablatronix

Following on from a [Discord discussion](https://discord.com/channels/638610460567928832/638610461109256194/898730354507137054) with @tablatronix: 1. Add a read-only volume mapping for Docker socket. 2. Restructure the defaults configuration scheme to support "additions", comprising two files: - `inputs.docker.conf` - provided by @tablatronix - `inputs.mqtt_consumer.conf` - recovered from the original gcgarner default configuration file. Rather than a ".bak" file, the reference version of the telegraf configuration file (the one that ships with the DockerHub image) is provided as: ``` ~/IOTstack/volumes/telegraf/telegraf-release.conf ``` Documentation updated on master branch.

…tainer-experimental 20211015 Telegraf - defaults - experimental branch - PR 3 of 3

…imental 20211011 Home Assistant - experimental branch - PR 3 of 3

…air-experimental 20211005 Prometheus revamp - experimental branch - PR 3 of 3

20210924 Portainer - experimental branch - PR 3 of 3

20210917 Mosquitto - HTTP not HTTPS during build + health check - experimental branch - PR 3 of 3

…-experimental 20211002 MariaDB health check - experimental branch - PR 3 of 3

This PR began with a [Discord question](https://discord.com/channels/638610460567928832/638610461109256194/900627294798893056) and uncovered a small can of worms. 1. The [github.com/blynkkk/blynk-server](https://github.com/blynkkk/blynk-server) repository appears to have been deleted. The replacement fork is at [github.com/Peterkn2001/blynk-server](https://github.com/Peterkn2001/blynk-server). This requires a change to the Dockerfile. 2. There are several problems with the `directoryfix.sh` mechanism which are best shown by example: * By default, the script lacks execute permission: ``` $ cd ~/IOTstack $ ls -l ./.templates/blynk_server/directoryfix.sh -rw-r--r-- 1 pi pi 2524 Sep 6 11:39 ./.templates/blynk_server/directoryfix.sh ``` * Correcting, executing and examining the result: ``` $ chmod +x ./.templates/blynk_server/directoryfix.sh $ ./.templates/blynk_server/directoryfix.sh Sample properties files created in ~/IOTstack/volumes/blynk_server/data/config Make sure you edit the files with your details, and restart the container to take effect. $ tree ./volumes/blynk_server/ ./volumes/blynk_server/ └── data └── config ├── mail.properties └── server.properties ``` * That folder structure is incorrect. The service definition declares: ``` volumes: - ./volumes/blynk_server/data:/data - ./volumes/blynk_server/config:/config ``` and the Dockerfile expects `/config` in the `-serverConfig` and `-mailConfig` arguments: ``` ENTRYPOINT ["java", "-jar", "/blynk/server.jar", "-dataFolder", "/data", "-serverConfig", "/config/server.properties", "-mailConfig", "/config/mail.properties"] ``` * Thus, a manual fix is needed before the container initialises properly: ``` $ sudo mv ./volumes/blynk_server/data/config ./volumes/blynk_server/ $ tree ./volumes/blynk_server/ ./volumes/blynk_server/ ├── config │ ├── mail.properties │ └── server.properties └── data ``` * These problems could be corrected by altering `directoryfix.sh` but it still leaves the basic problem common to all "directoryFix" bandaids: the script only runs at menu time, or when the user "just knows" to run it by hand, and doesn't handle container self-repair automatically each time the container starts. 3. The existing Dockerfile references `adoptopenjdk/openjdk14` as its base image. At the time of writing (2021-10-23) the [DockerHub page](https://hub.docker.com/r/adoptopenjdk/openjdk14) claims to have been updated 6 months ago but the actual image that downloads on Raspbian is significantly older: ``` $ docker images | grep -e "^REPOSITORY" -e "^adoptopenjdk" REPOSITORY TAG IMAGE ID CREATED SIZE adoptopenjdk/openjdk14 latest 4b3c72387798 15 months ago 403MB ``` There is an example Dockerfile at [github.com/Peterkn2001/blynk-server](https://github.com/Peterkn2001/blynk-server/blob/master/server/Docker/Dockerfile) which uses `ubuntu` as its base image. This implies that the current Blynk Server fork is being tested on Ubuntu. It is also clear that Ubuntu is getting a lot more maintenance: ``` $ docker images | grep -e "^REPOSITORY" -e "ubuntu" REPOSITORY TAG IMAGE ID CREATED SIZE ubuntu latest 897590a6c564 7 days ago 49.8MB ``` 4. The existing Dockerfile is tightly-coupled with the Blynk-Server version number. I have abstracted this using an `ARG` statement: ``` ARG BLYNK_SERVER_VERSION=0.41.16 ``` In the Dockerfile, this defaults to the current version but can be altered by the end user in the compose file: ``` blynk_server: build: context: ./.templates/blynk_server/. args: - BLYNK_SERVER_VERSION=0.41.16 ``` A user who wants to adopt a later version can alter the compose file and "build" the container. 5. The blynk server appears to listen to a large number of ports (at least 587, 7443, 8080, 8081, 8082, 8440, 8441, 8442, 8443 & 9443). Three ports seem to be directly relevant: - 8080 http.port - 8440 hardware.mqtt.port - 9443 https.port Those ports have been: - exposed in the Dockerfile, adding 8440 which *is* mentioned in `server.properties`; and - declared in the default service definition, removing 8441 which is *not* mentioned in `server.properties`. Note: - The Dockerfile at [github.com/Peterkn2001/blynk-server](https://github.com/Peterkn2001/blynk-server/blob/master/server/Docker/Dockerfile) attempts to expose: ``` EXPOSE ${HARDWARE_MQTT_PORT} ${HARDWARE_MQTT_PORT_SSL} ${HTTP_PORT} ${HTTPS_PORT} ``` `HARDWARE_MQTT_PORT_SSL` is *probably* intended to be port 8441 but it is not actually defined so it evaluates to a null. 6. Container self-repair is implemented in the now fairly well-established fashion: - An `iotstack_defaults` folder in the template is copied into the image. In this case, it contains the contents of the `config` directory. - A `docker-entrypoint.sh` in the template is copied into the image. When the container is brought up, this script executes first and performs self-repair, then "execs" the original command over the top. 7. Support for three environment variables: - `TZ=Etc/UTC` - the container already has timezone support so this just makes it clear that it can be activated. - `IOTSTACK_UID=1000` & `IOTSTACK_GID=1000` control the ownwership assigned to the "config" directory and its contents during self-repair. Defaults to "nobody" if omitted. 8. Documentation not changed.

References: 1. [Discord question](https://discord.com/channels/638610460567928832/638610461109256194/909831079253393419). 2. [GitHub deconz-community](https://github.com/deconz-community/deconz-docker). Changes recommended from Reference #2: * Image from: - `marthoc/deconz:stable` to: - `deconzcommunity/deconz` * Right hand side of volumes mapping from: - `/root/.local/share/dresden-elektronik/deCONZ` to: - `/opt/deCONZ`

…air-experimental 20211023 Blynk Server - experimental branch - PR 3 of 3

…perimental 20211116 Deconz community - experimental branch - PR 3 of 3

Under 2.x versions of docker-compose, volumes statements in service definitions that have trailing slashes cause: ``` Error response from daemon: invalid mount config for type "bind": bind source path does not exist: ``` This problem only shows up on first install of a container (ie when the container's persistent storage area has not yet been initialised). There are 51 volumes statements across all current service definitions: ``` $ find ~/IOTstack/.templates -name "service.yml" -exec grep -H '\- \./volumes' {} \; | wc -l 51 ``` Of those, 5 have a trailing "/" on either or both sides: ``` $ find ~/IOTstack/.templates -name "service.yml" -exec grep -H '\- \./volumes' {} \; | grep -e '/:' -e '/$' /home/pi/IOTstack/.templates/telegraf/service.yml: - ./volumes/telegraf/:/etc/telegraf /home/pi/IOTstack/.templates/pihole/service.yml: - ./volumes/pihole/etc-pihole/:/etc/pihole/ /home/pi/IOTstack/.templates/pihole/service.yml: - ./volumes/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/ /home/pi/IOTstack/.templates/diyhue/service.yml: - ./volumes/diyhue/:/opt/hue-emulator/export/ /home/pi/IOTstack/.templates/deconz/service.yml: - ./volumes/deconz/:/opt/deCONZ ``` This pull request removes those extraneous trailing slashes. Changes do not affect current docker-compose or container behaviour.

…imental 20211116 volume-mounts - experimental branch - PR 3 of 3

Pull Requests [PR387](#387), [PR388](#388), [PR389](#389) added a port mapping of `9322:3306` to facilitate backup and restores - so the routines could determine when the MariaDB service was ready for business. The need for this was superseded by PRs [416](#416), [417](#417) and [418](#418). It is sufficient for backup and restore routines to run the health check and rely on the return status. This PR removes the `9322:3306` as no longer needed. It will also avoid the need to protect the port with an iptables rule in situations where the host is exposed to the network. Signed-off-by: Phill Kelley <[email protected]>

@ukkopahis

Following a suggestion from @ukkopahis, this pull request proposes logging self-repair activities. Guard messages make it clear when self-repair begins and ends: ``` [IOTstack] begin self-repair … [IOTstack] end self-repair ``` Between the guard messages: * `-v` option added to `rsync` * `-c` option added to `chown` These cause the respective processes to log any changes they make to persistent storage. Example. Assume `config/filter.acl` has been deleted and ownership of the `pwfile` folder and its contents has been changed to "pi:pi". Self-repair needs to restore `filter.acl` and restore the ownership to "1883:1883": ``` [IOTstack] begin self-repair sending incremental file list ./ config/ config/filter.acl pwfile/ sent 326 bytes received 50 bytes 752.00 bytes/sec total size is 1,077 speedup is 2.86 changed ownership of '/mosquitto/pwfile/pwfile' to 1883:1883 [IOTstack] end self-repair ``` Signed-off-by: Phill Kelley <[email protected]>

…r-logging-experimental 20211220 mosquitto-selfRepair-logging - experimental branch - PR 3 of 3

…-port-experimental 20211215 nextcloud_db - exposed port - experimental branch - PR 3 of 3

Deprecates Dockerfile-based build in favour of environment variables that implement the same behaviour. Dockerfile retained to avoid introducing a breaking change. A notification is displayed each time the Dockerfile is run: ``` *** DEPRECATION NOTICE: Please read IOTstack Zigbee2MQTT documentation: *** https://sensorsiot.github.io/IOTstack/Containers/Zigbee2MQTT/ ``` The intention is that user attention will be drawn to the need to update their service definitions. The revised service definition: * includes a `depends_on` clause tying Zigbee2MQTT to Mosquitto (the default arrangement for IOTstack). * reduces the `devices` list to just `- /dev/ttyAMA0:/dev/ttyACM0` in favour of extended "how to" documentation for device discovery. Addresses issues raised in #402, #423 and #538. Documentation not changed. Signed-off-by: Phill Kelley <[email protected]>

…ental 20220404 Zigbee2MQTT - experimental branch - PR 3 of 3

Adds health-check functionality to Grafana and InfluxDB 1.8, as discussed in #415. Health-check functionality already added to Mosquitto via #410. Closes #415 Signed-off-by: Phill Kelley <[email protected]>

Adds template for InfluxDB 2 container. Documentation on Master branch. Signed-off-by: Phill Kelley <[email protected]>

20220602 InfluxDB 2 - experimental branch - PR 3 of 3

…ental 20220517 Grafana InfluxDB HealthCheck - experimental branch - PR 3 of 3

A Discord thread starting at https://discord.com/channels/638610460567928832/638610461109256194/1005812386688680006 revealed that the Domoticz would not function properly on a clean install. The symptom was either a 400 or a 404 error, depending on the URL. Three issues identified with existing service definition: 1. Wrong image base. Should be "lscr.io/linuxserver/domoticz". 2. Wrong image tag. Should be "latest". 3. `network_mode: bridge`. It has never been clear what `network_mode: bridge` is intended to do. It is the only container with this option. While it may once have been needed, its presence now appears to prevent the container from responding correctly on port 8083. Signed-off-by: Phill Kelley <[email protected]>

20220810 domoticz - experimental branch - PR 3 of 3

… of 3 WireGuard has started renaming the `custom-services.d` and `custom-cont-init.d` directories to have random suffixes, along with the following README.txt: ``` ******************************************************** ******************************************************** * * * !!!! * * Custom scripts or services found in legacy locations * * !!!! * * Please move your custom scripts and services * * to /custom-cont-init.d and /custom-services.d * * respectively to ensure they continue working. * * * * Visit https://linuxserver.io/custom for more info. * * * ******************************************************** ******************************************************** ``` Some existing installations have also failed. Remote clients are unable to connect with `docker logs wireguard` cycling the following messages: ``` s6-supervise custom-svc-README.txt (child): fatal: unable to exec run: Exec format error s6-supervise custom-svc-README.txt: warning: unable to spawn ./run - waiting 10 seconds ``` The container does not go into a restart loop so `docker ps` does not alert the user to the situation. This PR: 1. implements the required changes to the WireGuard service definition; 2. provides a script to assist with the necessary folder restructuring; 3. adds a section to the IOTstack WireGuard documentation (master branch) to explain the process. Signed-off-by: Phill Kelley <[email protected]>

… of 3 Adds `nodered_version_check.sh` script to scripts folder (previously available via [gist](https://gist.github.com/Paraphraser/c8939213faf2de8a10f2a1f67452b0c1#-useful-script-nodered_version_check-)). Documentation added to master branch. Signed-off-by: Phill Kelley <[email protected]>

`raymondmm/tasmoadmin` on DockerHub was last updated two years ago. Switches image to `ghcr.io/tasmoadmin/tasmoadmin:latest`. Also adds `TZ` to template. Removes reference to `iotstack_nw`. Signed-off-by: Phill Kelley <[email protected]>

Per issue #620, the default `config.yml` should reference: - `prometheus-cadvisor:8080` not `cadvisor:8080` - `prometheus-nodeexporter:9100` not `nodeexporter:9100` Signed-off-by: Phill Kelley <[email protected]>

…ntal 2022-11-08 Prometheus defaults - experimental branch - PR 3 of 3

…ntal 2022-10-28 tasmoadmin - experimental branch - PR 3 of 3

…rimental 2022-10-11 Node-RED version-check script - experimental branch - PR 3…

…estructure-experimental 2022-10-01 WireGuard volumes restructure - experimental branch - PR 3…

Adds dependency checking for jq and rclone. Signed-off-by: Phill Kelley <[email protected]>

Adds ring-mqtt service definition. Documentation added to master branch. Signed-off-by: Phill Kelley <[email protected]>

Signed-off-by: Phill Kelley <[email protected]>

2022-12-24 ring-mqtt - experimental branch - PR 3 of 3

…perimental 2022-12-02 Wireguard helper script - experimental branch - PR 3 of 3

…3 of 3 See #648 for background to this PR. Consequential changes: * harmonises template service definition by removing reference to port 443 and re-aligning entries. * harmonises default environment variables to be the same as master branch (including comments). * removes obsolete `networks:` clause. * removes handling for `TZ`, `WEBPASSWORD`, `DNS1` and `DNS2` from the modifiable environment. The DNS pair are a consequence of overall harmonisation. Signed-off-by: Phill Kelley <[email protected]>

2023-01-22 Pi-hole admin password changes - experimental branch - PR 3 of 3

* ring-mqtt had `service.yml` but no `template.yml`, renamed. * adhuardhome and octoprint had both `service.yml` and `template.yml`. Resolved in favour of `template.yml`. Signed-off-by: Phill Kelley <[email protected]>

1. Adds pgAdmin4: - service definition 2. Consequential changes to PostgreSQL container: - Adopted modern syntax for environment variables (`.env` support). - Removed obsolete `iotstack_nw` definition. - Added volume path for backup folder to support IOTstackBackup. Signed-off-by: Phill Kelley <[email protected]>

Adjusts Dockerfile to cope with rename of internal file path `/defaults/my.cnf` to `/defaults/custom.cnf`. Strategy is to check for the presence of both files and then apply the stability patches to the first match. This should mean that the Dockerfile is backwards compatible with images that use `my.cnf`. Signed-off-by: Phill Kelley <[email protected]>

2023-01-29 templates - experimental branch

2023-02-07 pgadmin4 - experimental branch

2023-02-14 MariaDB Dockerfile - experimental branch - PR 3 of 3

Changes external HTTPS port for Blynk Server from 9443 to 9444. This is a consequence of PR #671 claiming 9443 for Portainer-CE. Also adds external port 9443 to Portainer-CE on old-menu branch to keep this branch in sync with the master branch changes made via #671. Signed-off-by: Phill Kelley <[email protected]>

…ental 2023-03-09 Blynk-server https port - experimental branch - PR 3 of 3

Pins `node-red-node-serialport` to version `0.15.0`. This seems to be the only version that works with current Node-RED (3.0.2). Test case showing version `0.15.0` working included with #681. Also includes links to related issues on other repositories which led to this solution. Signed-off-by: Phill Kelley <[email protected]>

Adds `.env` to .gitignore. Also harmonises ignore file across all three branches. Signed-off-by: Phill Kelley <[email protected]>

2023-05-15 .gitignore harmonisation - experimental branch - PR 3 of 3

2023-04-09 Node-RED pin serial node - experimental branch - PR 3 of 3

Commits on Dec 22, 2020

Fixed sudo issue inside bash functions

Slyke committed Dec 22, 2020

Configuration menu

View commit details

Copy full SHA for fbf67e4

Browse repository at this point

Copy the full SHA

fbf67e4 View commit details

Browse the repository at this point in the history

Commits on Jan 20, 2021

Added checks for error paths

Slyke committed Jan 20, 2021

Configuration menu

View commit details

Copy full SHA for 75b4636

Browse repository at this point

Copy the full SHA

75b4636 View commit details

Browse the repository at this point in the history

Commits on Jan 23, 2021

Added basic volume options

Slyke committed Jan 23, 2021

Configuration menu

View commit details

Copy full SHA for 4c9a817

Browse repository at this point

Copy the full SHA

4c9a817 View commit details

Browse the repository at this point in the history

Commits on Feb 21, 2021

Tested and fixed many services

Slyke committed Feb 21, 2021

Configuration menu

View commit details

Copy full SHA for 117205d

Browse repository at this point

Copy the full SHA

117205d View commit details

Browse the repository at this point in the history

Commits on Feb 24, 2021

Added build yaml viewer on history page

Slyke committed Feb 24, 2021

Configuration menu

View commit details

Copy full SHA for 4f755bc

Browse repository at this point

Copy the full SHA

4f755bc View commit details

Browse the repository at this point in the history

Commits on Mar 5, 2021

Added install build option

Slyke committed Mar 5, 2021

Configuration menu

View commit details

Copy full SHA for f3e0cd0

Browse repository at this point

Copy the full SHA

f3e0cd0 View commit details

Browse the repository at this point in the history

Commits on Mar 23, 2021

Got PyCLI menu loading API services

Slyke committed Mar 23, 2021

Configuration menu

View commit details

Copy full SHA for df440f1

Browse repository at this point

Copy the full SHA

df440f1 View commit details

Browse the repository at this point in the history

Commits on Mar 27, 2021

Added basic issue checking on pycli.

Slyke committed Mar 27, 2021

Configuration menu

View commit details

Copy full SHA for 1413a83

Browse repository at this point

Copy the full SHA

1413a83 View commit details

Browse the repository at this point in the history

Commits on Mar 29, 2021

Added build checking to PyCLI menu

Slyke committed Mar 29, 2021

Configuration menu

View commit details

Copy full SHA for e86eae7

Browse repository at this point

Copy the full SHA

e86eae7 View commit details

Browse the repository at this point in the history

Commits on Apr 27, 2021

Added in option detection from API.

Slyke committed Apr 27, 2021

Configuration menu

View commit details

Copy full SHA for 7f7ccf7

Browse repository at this point

Copy the full SHA

7f7ccf7 View commit details

Browse the repository at this point in the history

PyCLI, WUI, API upgrades #291

Are you sure you want to change the base?

PyCLI, WUI, API upgrades #291

Commits on Dec 22, 2020

Commits on Jan 15, 2021

Commits on Jan 16, 2021

Commits on Jan 17, 2021

Commits on Jan 19, 2021

Commits on Jan 20, 2021

Commits on Jan 23, 2021

Commits on Feb 12, 2021

Commits on Feb 13, 2021

Commits on Feb 14, 2021

Commits on Feb 15, 2021

Commits on Feb 16, 2021

Commits on Feb 19, 2021

Commits on Feb 21, 2021

Commits on Feb 22, 2021

Commits on Feb 24, 2021

Commits on Feb 28, 2021

Commits on Mar 2, 2021

Commits on Mar 5, 2021

Commits on Mar 6, 2021

Commits on Mar 7, 2021

Commits on Mar 8, 2021

Commits on Mar 9, 2021

Commits on Mar 12, 2021

Commits on Mar 16, 2021

Commits on Mar 17, 2021

Commits on Mar 18, 2021

Commits on Mar 19, 2021

Commits on Mar 23, 2021

Commits on Mar 27, 2021

Commits on Mar 29, 2021

Commits on Mar 30, 2021

Commits on Mar 31, 2021

Commits on Apr 4, 2021

Commits on Apr 27, 2021

Commits on Apr 30, 2021

Commits on May 4, 2021

Commits on May 5, 2021

Commits on May 7, 2021

Commits on May 8, 2021

Commits on May 11, 2021

Commits on May 13, 2021

Commits on May 14, 2021

Commits on May 24, 2021

Commits on May 27, 2021

Commits on May 28, 2021

Commits on May 29, 2021

Commits on Jun 4, 2021

Commits on Jun 10, 2021

Commits on Jun 12, 2021

Commits on Jun 14, 2021

Commits on Jun 19, 2021

Commits on Jun 21, 2021

Commits on Jul 13, 2021

Commits on Aug 9, 2021

Commits on Aug 24, 2021

Commits on Aug 26, 2021

Commits on Aug 27, 2021

Commits on Sep 4, 2021

Commits on Sep 17, 2021

Commits on Sep 24, 2021

Commits on Sep 30, 2021

Commits on Oct 2, 2021

Commits on Oct 5, 2021

Commits on Oct 11, 2021

Commits on Oct 15, 2021

Commits on Oct 17, 2021

Commits on Oct 23, 2021

Commits on Nov 16, 2021

Commits on Nov 20, 2021

Commits on Nov 28, 2021

Commits on Dec 3, 2021

Commits on Dec 14, 2021

Commits on Dec 20, 2021

Commits on Jan 19, 2022

Commits on Apr 5, 2022

Commits on Apr 26, 2022