From b25542805cd47b75c4e5987e4bc770277e3015a3 Mon Sep 17 00:00:00 2001
From: Efraim Flashner
Date: Wed, 9 Sep 2020 08:20:58 +0000
Subject: Use per-service guix profiles

---
 README | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'README')

diff --git a/README b/README
index dbe7b39..ab280e3 100644
--- a/README
+++ b/README
@@ -18,3 +18,6 @@ $ herd load root .config/shepherd/init.d/bar.scm
 The second command will load the code in `bar.scm` into `shepherd`, and if the service is configured to start automatically at startup it will start immediately. This process should not affect the other running services.
 
 To use shepherd's herd command, assuming you have permissions granted in /etc/sudoers, the command is 'sudo -u shepherd /home/shepherd/.guix-profile/bin/herd status'.  Adding a bash alias, such as "alias herd-herd='sudo -u shepherd /home/shepherd/.guix-profile/bin/herd'", will make it easier to interact with shepherd without needing to switch to the shepherd user.  The logs for the various shepherd services are located in /home/shepherd/logs/ but are not yet timestamped.  The log for shepherd itself is in /home/shepherd/.config/shepherd/shepherd.log.  There is not yet a way to change this from a config file.
+
+*Per service Guix profiles*
+Each service gets its own guix profile. This us to upgrade each service individually. If a specialized channel is needed then the command would be `guix pull --channels=/path/to/channels/file --profile=/path/to/profile`
-- 
cgit v1.2.3