The (oddly named) procedure “guix-infect” in (gnu machine digital-ocean) contains a Bash script that installs Guix 1.0.1 and sets the GUILE_LOAD_PATH to that of Guile 2.2. Likewise, “add-static-networking” in the same module sets GUILE_LOAD_PATH to 2.2. It seems to me that this should be updated to install the latest version of Guix and set the load path to that of Guile 3.0. I also wonder if there might not be a better way to deploy Guix quickly, for example by using a relocatable pack of Guix and using “guix copy” instead of executing a shell script. -- Ricardo
Hello Ricardo, > I also wonder if there might not be a better way to deploy Guix quickly, > for example by using a relocatable pack of Guix and using “guix copy” > instead of executing a shell script. I think that building a Guix System image and creating a droplet out of it using the DigitalOcean API, as I described here[1] would be a better solution. Thanks, Mathieu [1]: https://othacehe.org/hosting-a-blog-using-only-scheme.html
Hi Mathieu, >> I also wonder if there might not be a better way to deploy Guix quickly, >> for example by using a relocatable pack of Guix and using “guix copy” >> instead of executing a shell script. > > I think that building a Guix System image and creating a droplet out of > it using the DigitalOcean API, as I described here[1] would be a better > solution. Yes, this seems better than installing Guix on an existing system (which costs time and possibly expensive bandwidth), and to replace the running system with it. FWIW, I wrote Guile AWS[1], which may be useful for doing the same with AWS as a backend. -- Ricardo [1]: https://git.elephly.net/?p=software/guile-aws.git
This is no longer the case. The module no longer references Guile 2, and it installs the latest version of Guix. -- Ricardo