Hi, Thank you for your feedback.
On Wed, 18 Nov 2020 at 14:53, Ryan Prior <ryanpr...@hey.com> wrote: >> Multiple isolated environments on a single host >> Preserve volume data when containers are created >> Only recreate containers that have changed >> Variables and moving a composition between environments [...] > For example, a common thing I do with docker-compose is to provide a compose > file with a service I'm working on that brings up the service with all its > dependencies (eg databases, proxies, etc.) in a dev configuration, with the > source code from the repository mapped into the container and live-reload > enabled. That creates a "two-step" dev environment for the service: you clone > the repo then run "docker-compose up." Do you have configuration files of minimal examples? Just to understand what you mean using concrete examples. > Hashicorp has been working on Waypoint[1], a free software tool to extend > that concept even further by adding deployment and release capabilities. Now > you clone a repo and you have one tool to build, deploy and release the > software contained therein. > > I'm interested to use Guix for similar purposes, but there are a few primary > obstacles in the way: > 1) I don't have enough experience yet defining systems using Guix similar to > what I'd define using docker-compose, and I haven't found documentation or > examples yet that makes it seem within reach > 2) The machines I'm deploying to run Kubernetes, not Guix System, so if I do > use Guix to build a bundle for deployment its utility ends when I export to a > Docker container image. Thanks for pointing this out. > 3) I collaborate with developers who use macOS and Windows and so can't > easily install and use Guix. I speak for myself, the idea is to build Docker images using Guix for this case. Otherwise, I do not know if it is worth but someone pointed this [1] for Windows. 1: <https://github.com/giuliano108/guix-packages/blob/master/notes/Guix-on-WSL2.md> All the best, simon
