From: Thomas Sigurdsen <thomas.sigurdsen@gmail.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Webservices and Shepherd
Date: Sun, 2 Apr 2017 11:44:26 +0200 [thread overview]
Message-ID: <20170402114426.4c656028@hitpoints> (raw)
Hi Guix!
I'm sending two threads with the same intro, read below the line for the
questions.
I've been playing around with guixsd on my day-to-day work laptop for a month
or so now and have to say I'm thoroughly happy about how everything is put
together and mostly _just works_.
I'll note that I'm still very much learning guile and scheme. But the manual
(https://www.gnu.org/software/guile/manual/) is amazing.
-------------------------------------------------------------------------------------------------
I will, over the coming week or so, begin setting up a server (for web pages,
file sharing and hopefully email).
Webservices: Is it preferred to put their "program files" in package
definitions and telling shepherd how to run them in services?
Are there any examples of a guixsd server config with multiple web services
out there?
And when it comes to shepherd: I've seen a few configs where shepherd is
running as a user in addition to root. It looks like this is a good way to
separate webservices and similar, maybe even giving them separate users. But
does it mean shepherd is running multiple instances, increasing overhead and
difficulty of management (as in how do I know which shepherd I'm talking to
and so on)?
My entire configuration with homemade modules can be found at:
https://notabug.org/thomassgn/guixsd-configuration
next reply other threads:[~2017-04-02 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 9:44 Thomas Sigurdsen [this message]
2017-04-03 13:50 ` Webservices and Shepherd Ludovic Courtès
2017-04-03 15:56 ` Alex Kost
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=20170402114426.4c656028@hitpoints \
--to=thomas.sigurdsen@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).