Giacomo Leidi

I was never able to remember any #Guile command line parsing API, so I did the natural thing to do: I created another one from scratch.

https://fishinthecalculator.me/blog/arguments-parsing-in-guile.html

the API is very small, enough to fit in my head. reach out if you have any feedback. I think this can be useful in many small scripts, maybe also the ones generated from #Guix program-file gexps.

Last year, the ability to declaratively provision OCI containers, networks and volumes was introduced in #guix ( https://guix.gnu.org/manual/devel/en/guix.html#index-oci_002dservice_002dtype ). This allows for managing OCI containers with the Shepherd and having them integrated and customizable via Guix code, see for example #gocix .

Many people are used to manage their OCI containers with docker compose but want to migrate to Guix OCI services to benefit from Guix rollbacks and further features.

https://codeberg.org/fishinthecalculator/guix-compose does exactly that, you run

guix compose import docker-compose.yml

and you get the corresponding Guix code to instantiate the same resources. You can just paste it in your configuration and you run it.

next steps could be running containers as transient Shepherd services and trying to parse @coopcloud@social.coop recipes and output Guix code

@spritely@social.coop is it crazy to imagine an #ocapn netlayer for #spritely #goblins over #p2panda ? We'd need some #guile bindings for the library but I guess if it works on libp2p it may be possible for other p2p networks.