unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>, guix-devel@gnu.org
Subject: Re: Guix containers 'advertised' in git repos
Date: Thu, 27 Aug 2020 12:53:39 +0200	[thread overview]
Message-ID: <868se0e4wc.fsf@gmail.com> (raw)
In-Reply-To: <20200810103658.swmptuhdfv4w2why@thebird.nl>

Hi Pjotr,

On Mon, 10 Aug 2020 at 12:36, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> We are using Guix containers for deployment and software development.
> I was thinking it would be nice to advertise them in the git repos.
>
> Maybe we can standardise on that. What I have now is have a file
>
>   .git-deploy
>
> for deployment. E.g.,
> https://github.com/encryption4genetics/HEGP-website/blob/master/.guix-deploy
>
> and 
>
>   .git-dev 
>
> for development. E.g.,
> https://github.com/genetics-statistics/GEMMA/blob/master/.guix-dev
>
> These are just examples and can be generalised with a manifest. And
> I should probable use plain guix instead of ~/opt/guix/bin/guix ;).
>
> But maybe we can document a 'standard' for people to follow that allow
> for quickly finding the build using guix and deploying with a single
> command
>
>     sh .guix-deploy

I am not convince that a shell file should be the “standard” and instead
“augmented” manifest files seem more elegant, as suggested for example
here:

  https://lists.gnu.org/archive/html/guix-devel/2020-07/msg00005.html


Cheers,
simon


  parent reply	other threads:[~2020-08-27 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 10:36 Guix containers 'advertised' in git repos Pjotr Prins
2020-08-10 14:53 ` David Dashyan
2020-08-27 10:53 ` zimoun [this message]
2020-08-28 10:33 ` Ludovic Courtès

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=868se0e4wc.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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).