This repo contains the files used to run shepherd services.
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
Efraim Flashner 3ca5af0178 covid19-pubseq: New service. 1 mês atrás
cron cron: Add pubmed cronjob 4 meses atrás
shepherd covid19-pubseq: New service. 1 mês atrás
20200503-channels.scm bnw: Use an older commit. 2 meses atrás
README README: Update 3 meses atrás
run_bnw.sh bnw, ratspub: Update service. 1 mês atrás
run_covid19-pubseq.sh covid19-pubseq: New service. 1 mês atrás
run_gitea-dump.sh gitea: Move service to new location 3 meses atrás
run_gitea.sh gitea: Move service to new location 3 meses atrás
run_ipfs.sh initial commit 5 meses atrás
run_power.sh initial commit 5 meses atrás
run_ratspub.sh bnw, ratspub: Update service. 1 mês atrás
run_rn6app.sh initial commit 5 meses atrás
run_singlecell.sh shepherd: fix singlecellrshiny 4 meses atrás
running_ratspub docs: document running ratspub 3 meses atrás
update_archive-pubmed.sh update pubmed archive: Use edirect 4 meses atrás
user-shepherd.service systemd: Add service to start shepherd at start-up. 4 meses atrás

README

This repo contains the files used to run shepherd services.

The `shepherd` and `cron` directories go in `.config`

The shell scripts sit in the home directory.

The systemd service is to start shepherd automatically on system boot.

Working with Shepherd Services

Each service is stored in a separate file. This allows us to reload individual services without needing to restart all of the services in one go. In order to see which services are available run the command `herd status`. 'Started' services are currently running, 'Stopped' services are not running but are still loaded, and 'One-shot' are services which are not running but run a one-off script or service.

The services are setup so that they have code that is run when it is started and continues to run until it is stopped. Sometimes that code can call other shell scripts in the home directory. If the primary code in the service needs to be changed then the service needs to be reloaded in accordance to a process that will allow it to be reloaded without stopping all the other services. In our example the service is `foo` and it is located in a file `bar.scm`.

$ herd stop foo
$ 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.