Hello, Pjotr Prins <pjotr.publi...@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 <m...@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’.
