all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hafeez Bana <hafeez.bana@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Guix questions on sharing developer envs
Date: Mon, 22 May 2023 10:52:56 +0100	[thread overview]
Message-ID: <CAGNLXrnk03JUTE1ioLP1N57jfroYzw-hU2_NLXeQMfaM2F=cZA@mail.gmail.com> (raw)
In-Reply-To: <CAGNLXrkMZk2r7p66TUXGKxYxZxQdR1N7wE65fv05a874ARfjiw@mail.gmail.com>

Any takers? I meant XDG above.

On Sat, May 20, 2023 at 2:52 PM Hafeez Bana <hafeez.bana@gmail.com> wrote:

> Hi,
>
> I am planning to use guix for sharing dev environments under non-root unix
> accounts across developers.
>
> These environment run services like mysql, a webserver etc. Installing
> such software is trivial. What is the best practice for running this
> software? A couple of pointed questions
>
> 1) What is the best/accepted way to store configuration and state data for
> such services? It the XFG format applicable?
> 2) If a package ships with a set of starting configs/state data which a
> developer can use to bootstrap and modify his setup. What is the best way
> to 'initialize this config/state'? Is just a link to the GNU-store enough
> 3) What is the best way to run long lived (aka outside a shell) services
> running services based around this software?
>
> I've already asked this question in a round about way. Some people have
> pointed to existing configs - but these are for running whole systems in a
> container. I need something a developer can bootstrap into and modify that
> could eventually run as a container in a prod env.
>
> Thanks,
> Hafeez
>

      reply	other threads:[~2023-05-22 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-20 13:52 Guix questions on sharing developer envs Hafeez Bana
2023-05-22  9:52 ` Hafeez Bana [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGNLXrnk03JUTE1ioLP1N57jfroYzw-hU2_NLXeQMfaM2F=cZA@mail.gmail.com' \
    --to=hafeez.bana@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.