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
Hi! We do the same thing, kind of, but due to our CLA restrictions we have everything in separate repository. https://github.com/ipdb/bigchaindb-guix I've named the file "activate" which is python's idiom taken from virtualenv. And it creates persistent dev environment in ".genv" directory (maybe .guix-profile is a better name). It would be cool to have an naming conventions in place, the only problem I see here is that guix is capable of so much stuff it is hard to predict ways people are going to be using it. -- David aka zzappie
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
Hello, Pjotr Prins <pjotr.public12@thebird.nl> skribis: > 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 [...] David Dashyan <mail@davie.li> skribis: > We do the same thing, kind of, but due to our CLA restrictions we have > everything in separate repository. > > https://github.com/ipdb/bigchaindb-guix > > I've named the file "activate" which is python's idiom taken from There’s a rather widespread convention for ‘guix.scm’, to be passed to ‘guix environment -l’ or ‘guix package -f’. However, there’s currently no tool to declare the container parameters, which is why your ‘.guix-deploy’ file above is essentially a shell script. A long time ago Dave Thompson suggested having an <environment> (or similar) data type on top of <manifest>, which would describe that sort of thing. Perhaps something to keep in mind for ‘guix shell’? Ludo’.