unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ryan Prior <rprior@protonmail.com>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Named environments
Date: Fri, 10 Sep 2021 23:06:43 +0000	[thread overview]
Message-ID: <d-pJcNuOoDSaDMRNBYkeakXFM7HwedCsyk4vNz0O6qdtilD_efRWA3Cj58FYwzJpuFyahUHmIFXa2_7V_trvdXG-6vm8n_J0_9cpq9y8OHY=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1205 bytes --]

             reply	other threads:[~2021-09-10 23:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 23:06 Ryan Prior [this message]
2021-09-11  8:59 ` Named environments Domagoj Stolfa
2021-09-12 19:33 ` Sarah Morgensen
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='d-pJcNuOoDSaDMRNBYkeakXFM7HwedCsyk4vNz0O6qdtilD_efRWA3Cj58FYwzJpuFyahUHmIFXa2_7V_trvdXG-6vm8n_J0_9cpq9y8OHY=@protonmail.com' \
    --to=rprior@protonmail.com \
    --cc=guix-devel@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 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).