diff options
| author | Pjotr Prins | 2024-06-21 05:49:56 -0500 |
|---|---|---|
| committer | Pjotr Prins | 2024-06-21 05:50:06 -0500 |
| commit | 02a6d9ebc2e2c160874e2f52412cfc7be67b7231 (patch) | |
| tree | eef1842ae4683d6416e61594925d454b956e7990 /issues | |
| parent | fb231ce4e8d09c1f910a5be27a76b914149b7a24 (diff) | |
| download | gn-gemtext-02a6d9ebc2e2c160874e2f52412cfc7be67b7231.tar.gz | |
genecup: updated information - now running as a container
Diffstat (limited to 'issues')
| -rw-r--r-- | issues/genecup-running-as-root.gmi | 6 | ||||
| -rw-r--r-- | issues/per-service-profile-for-shepherd-services.gmi | 15 |
2 files changed, 17 insertions, 4 deletions
diff --git a/issues/genecup-running-as-root.gmi b/issues/genecup-running-as-root.gmi index c48924f..72d5704 100644 --- a/issues/genecup-running-as-root.gmi +++ b/issues/genecup-running-as-root.gmi @@ -1,5 +1,9 @@ # genecup is currently running as root on penguin2. +Is this still true for tux02? Fixed: genecup is now running as a container so we can close this. + +## Info + Currently when run using shepherd it fails like this: guix system: warning: Consider running 'guix pull' followed by @@ -32,7 +36,7 @@ A number of changes to different types of shepherd services (exec-command, make- * assigned: Efraim * type: failure * keywords: genecup, penguin2 -* status: unclear +* status: closed * priority: high ## Notes diff --git a/issues/per-service-profile-for-shepherd-services.gmi b/issues/per-service-profile-for-shepherd-services.gmi index 654a723..43c9118 100644 --- a/issues/per-service-profile-for-shepherd-services.gmi +++ b/issues/per-service-profile-for-shepherd-services.gmi @@ -1,11 +1,17 @@ # Each shepherd service needs its own guix profile. -Currently there are a bunch of shepherd services (on Penguin2, as user shepherd) who are using the global shepherd guix profile and loading guix-bioinformatics at service start time to start their services. This is bad because: +UPDATE: genecup is now running as a container on tux02. This is a model for getting rid of guix profiles. Note that we +do need to fixate guix-bioinformatics and guix-past channels *per* service. Otherwise updates are impossible. + +In time we may move to hosting these services in a guix system container (a VM). + +Currently there are a bunch of shepherd services (on tux02, as user shepherd) who are using the global shepherd guix profile and loading guix-bioinformatics at service start time to start their services. This is bad because: * we aren't using per-service guix-bioinformatics worktrees, so the branch changes between service refreshes * service start times are high because we have to rebuild the service (due to above) * services which are restarted are in an "untested" state until they work + ## Services which need to be migrated: * covid19-pubseq (uses shared (broken!) guix profile, uses shared config directory)(currently running by hand by Pjotr) @@ -22,6 +28,9 @@ Currently there are a bunch of shepherd services (on Penguin2, as user shepherd) ## Services which already have their own profile: +Note that the profiles essentially just contain the guix binary, acting like a time machine. It is +used to fire up a guix shell/environment: + * bnw * cronjob-gitea * cronjob-pubmed (genecup) @@ -34,8 +43,8 @@ Currently there are a bunch of shepherd services (on Penguin2, as user shepherd) ## Tags -* assigned: efraim +* assigned: efraim, pjotrp * type: bug -* status: unclear +* status: in progress * priority: high * keywords: shepherd, system administration |