From: Sarah Morgensen <iskarian@mgsn.dev>
To: Ryan Prior <rprior@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Named environments
Date: Sun, 12 Sep 2021 12:33:26 -0700 [thread overview]
Message-ID: <86zgshlhbt.fsf@mgsn.dev> (raw)
In-Reply-To: <d-pJcNuOoDSaDMRNBYkeakXFM7HwedCsyk4vNz0O6qdtilD_efRWA3Cj58FYwzJpuFyahUHmIFXa2_7V_trvdXG-6vm8n_J0_9cpq9y8OHY=@protonmail.com> (message from Ryan Prior on Fri, 10 Sep 2021 23:06:43 +0000)
Ryan Prior <rprior@protonmail.com> writes:
> Hey Guix.
>
> I've been thinking lately it would be convenient to create certain uniquely
> named execution environments on my machine. For example, I might have one
> set up with dependencies for my Python webapp & environment variables set to
> autoconnect to a Postgres server. I might have another that's got test
> dependencies and is containerized, such that it can only access the network
> & not the rest of my filesystem. Suppose I name these two "webapp" and
> "test" respectively.
>
> I picture running eg `guix env @webapp -- uvicorn main:app` to start my
> server, then `guix env @test -- pytest` to run my tests.
>
> I might write a wrapper in some scripting language that sets up this kind of
> system. Would anybody else be interested in using such a thing? Would it
> make sense to integrate this capability into Guix itself?
>
>Ryan
I like this idea! (And adding a built-in alias from "environment" to "env"
might be worth it, too.)
I actually use an ad-hoc version of this in my ~/.bashrc, using aliases. For
example,
alias geg='guix environment guix --pure --ad-hoc nano git git:send-email less help2man strace nss-certs'
This also lets me add on any ad-hoc packages at the end, like
geg dejagnu expect
However, an actual `guix env' could do a lot more! Like you allude to, being
able to essentially save the options of a `guix environment' invocation would
be great:
$ guix env --edit @test <lots of packages and environment options>
$ guix env @test -- pytest
But also imagine portable environments (used, for example, for project dev
environments, checked in with the source):
--8<---------------cut here---------------start------------->8---
$ guix env --export @myapp-test --pure -C -f guix.scm --ad-hoc strace coreutils
(environment "@myapp-test"
(load '("guix.scm"))
(ad-hoc-packages '("strace" "coreutils" "findutils"))
(flags '(pure container)))
--8<---------------cut here---------------end--------------->8---
Of course, this isn't entirely reproducible, as packages could change as you
update your Guix, even if you give a version spec (the same issue that exists
for manifests). So, we could pin the channel used to make the environment:
--8<---------------cut here---------------start------------->8---
$ guix env --export @myapp-test --pin-channels ...
(environment "@myapp-test"
(channels (list (channel (name 'guix)
(url ...)
(commit ...)))
(load '("guix.scm"))
(ad-hoc-packages '("strace" "coreutils" "findutils"))
(flags '(pure container))))
--8<---------------cut here---------------end--------------->8---
which, when evaluated, would internally do what `guix time-machine --channels
file' does.
These environments could then be used like:
$ guix env -e environment.scm @myapp-test
but that's quite long... perhaps we could allow `guix env' to automatically
read a "guix.scm" or "environment.scm" file in the current directory, and make
the environment definitions within available?
...so I definitely think there's room for such a feature in Guix :)
--
Sarah
next prev parent reply other threads:[~2021-09-12 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 23:06 Named environments Ryan Prior
2021-09-11 8:59 ` Domagoj Stolfa
2021-09-12 19:33 ` Sarah Morgensen [this message]
2021-09-13 8:08 ` zimoun
2021-10-06 13:29 ` Ludovic Courtès
2021-09-13 15:48 ` pinoaffe
2021-09-14 2:32 ` Ryan Prior
2021-09-14 6:27 ` Lars-Dominik Braun
2021-09-14 9:58 ` Pjotr Prins
2021-09-14 6:30 ` zimoun
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=86zgshlhbt.fsf@mgsn.dev \
--to=iskarian@mgsn.dev \
--cc=guix-devel@gnu.org \
--cc=rprior@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).