* .guix/rekahsoft/guix-config/vms/dash0-home-rekahsoft-ca.scm: Run grafana using the
oci-container-service.
* .guix/rekahsoft/guix-config/vms/git0-home-rekahsoft-ca.scm: Run gitea using the
oci-image-container-service.
* .guix/rekahsoft/guix-config/vms/my0-home-rekahsoft-ca.scm: Run organizr using the
oci-image-container-service.
* .guix/rekahsoft/guix-config/vms/prom0-home-rekahsoft-ca.scm: Run prometheus using the
oci-image-container-service.
* .guix/rekahsoft/guix-config/vms/searx0-home-rekahsoft-ca.scm: Run searx using the
oci-image-container-service.
* unguix/cloud0-home-rekahsoft-ca/nextcloud.sh: Removed as nextcloud is not longer in use.
* unguix/**.sh: Removed unneeded docker run scripts.
* unguix/loki-home-rekahsoft-ca/loki.sh: Remove /var/log volume (related change in promtail-config.yaml). This matches the docker-compose.yaml file introduced in this commit.
* unguix/loki-home-rekahsoft-ca/rsyslog.conf: Correct omfwd action target. Now that docker-compose is being used, and both the promtail and rsyslog containers are in the same non-default bridge network, we can depend on container dns resolution to handle the fact that promtail's ip is dynamic.
* unguix/loki-home-rekahsoft-ca/promtail-config.yaml (scrape_configs): Remove system /var/log job (its not necessary now that syslog is setup, and was primarily there for testing purposes in the first place).
* unguix/loki-home-rekahsoft-ca/docker-compose.yaml: New file; depreciates loki.sh. This enables correcting an issue with rsyslog configuration referencing the correct docker instance of promtail.
* unguix/loki-home-rekahsoft-ca/rsyslog.conf: rsyslog configuration used for syslog aggreator
* unguix/loki-home-rekahsoft-ca/promtail-config.yaml (scrape_configs): Add syslog scape configuration
* unguix/loki-home-rekahsoft-ca/loki.sh: Add rsyslog which acts as an syslog aggregator in front of promtail
* unguix/loki-home-rekahsoft-ca/loki-config.yaml (ingester): Add 'wal' (required after upgrade)
Adjust folder structure of bind mounts so metrics collected by prometheus are persisted
between container removals.
Note: the directory /var/lib/prometheus/data must be owned by `nobody:nogroup` for this to
work
