From: Alex Kost <alezost@gmail.com>
To: help-guix@gnu.org
Subject: Re: I need examples of Shepherd services without GuixSD
Date: Mon, 21 Aug 2017 21:20:12 +0300 [thread overview]
Message-ID: <87o9r8wzoj.fsf@gmail.com> (raw)
In-Reply-To: <20170820133523.rlspvsnoerdm3pnt@abyayala> (ng0@infotropique.org's message of "Sun, 20 Aug 2017 13:35:23 +0000")
ng0 (2017-08-20 13:35 +0000) wrote:
> As IRC wasn't very responsive:
>
> Does someone of you keep their Shepherd user-services, for shepherd running on
> non-GuixSD systems (side by side with systemd for example), online somewhere?
I have my Shepherd user config at
<https://github.com/alezost/shepherd-config>, but it is rather
complicated and too specialized for my needs, I'm not sure if it may be
helpful for anyone else.
David also has his config available:
https://git.dthompson.us/dotfiles.git/blob/HEAD:/dotfiles/.config/shepherd/init.scm
But why do you ask specifically about non-GuixSD system? AFAICT there
is absolutely no difference whether you run a user shepherd under GuixSD
or non-GuixSD system (I use my config on both GuixSD and ArchLinux).
--
Alex
prev parent reply other threads:[~2017-08-21 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 13:35 I need examples of Shepherd services without GuixSD ng0
2017-08-21 18:20 ` Alex Kost [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9r8wzoj.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).