fallback

3 files changed, 47 insertions, 3 deletions

diff --git a/topics/guix/guix-system-containers-and-how-we-use-them.gmi b/topics/guix/guix-system-containers-and-how-we-use-them.gmi
index 26baca8..f9d7253 100644
--- a/topics/guix/guix-system-containers-and-how-we-use-them.gmi
+++ b/topics/guix/guix-system-containers-and-how-we-use-them.gmi
@@ -72,3 +72,32 @@ Finally, we must also tell Guix not to accidentally garbage collect our containe
 ```
 # ln --force --symbolic /usr/local/bin/foo-container /var/guix/gcroots
 ```
+
+# Example
+
+On tux02 we run CI/CD system containers. The systemd config is simple:
+
+```
+[Unit]
+Description = Run genenetwork development container
+
+[Service]
+ExecStart = /usr/local/bin/genenetwork-development-container
+
+[Install]
+WantedBy = multi-user.target
+```
+
+where /usr/local/bin/genenetwork-development-container -> /gnu/store/8rkh8yjzqhcr3s5zl9mw8y4jh44fr5pr-run-container
+
+The code is currently running from Arun's $HOME from the git repo at
+
+=> https://git.genenetwork.org/gn-machines/
+
+Probably worth reading the
+
+=> https://git.genenetwork.org/gn-machines/tree/README.org README
+
+Here we focus on the production server setup running on test01:
+
+=> https://git.genenetwork.org/gn-machines/tree/production.scm
diff --git a/topics/systems/ci-cd.gmi b/topics/systems/ci-cd.gmi
index e9a24a3..6aa17f2 100644
--- a/topics/systems/ci-cd.gmi
+++ b/topics/systems/ci-cd.gmi
@@ -1,8 +1,6 @@
 # CI/ CD for genetwork projects
 
-We need to figure out/ discuss and document how to go about doing the whole automated testing and deployment, from pushing code to deployment to production.
-
-For a first, we need various levels of tests to be run, from unit tests to the more complicated ones like integration, performance, regression, etc tests, and of course, they cannot all be run for each and every commit, and will thus need to be staggered across the entire deployment cycle to help with quick iteration of the code.
+We need various levels of tests to be run, from unit tests to the more complicated ones like integration, performance, regression, etc tests, and of course, they cannot all be run for each and every commit, and will thus need to be staggered across the entire deployment cycle to help with quick iteration of the code.
 
 ## Tags
 
@@ -11,6 +9,7 @@ For a first, we need various levels of tests to be run, from unit tests to the m
 * status: in progress
 * priority: high
 * type: enhancement
+* status: closed
 
 ## Tasks
 
diff --git a/topics/systems/fallback.gmi b/topics/systems/fallback.gmi
index 1175d8f..e2bde6b 100644
--- a/topics/systems/fallback.gmi
+++ b/topics/systems/fallback.gmi
@@ -58,9 +58,25 @@ see also
 
 ## Guix system container
 
+* [X] Assess gemtext documentation
+* [ ] Check tux02 configurations
+* [ ] Set up guix channels
+* [ ] Set up guix gcroot
+* [ ] Update systemd
+* [ ] Add gn-guile to configuration
+* [ ] Test, test, test
 
+=> guix-system-containers-and-how-we-use-them More info
 
 ## Sheepdog monitoring
 
 * [ ] Move host to tb
 * [ ] Update all clients
+* [ ] Add monitoring new fallback services
+
+## Continuous updates
+
+* [ ] Mariadb
+* [ ] Redis
+* [ ] Auth
+* [ ] Files