Hi Rutherther, Rutherther <[email protected]> writes:
> This is not about how guix system or home work, it's 1. how guix works, > 2. how the services are done, not something that would be inherent > disadvantage of guix system/home. You are perfectly capable of making > such services as a user. I through that when a service type generate a config file, it would pass this file to an high level API that store the file in the store and then it was Guix System/Home that create a symbolic link to the stored file, depending of the active generation. I had read the manual and the cookbook in search of info about how to write a service type, but I maybe missed something about how a service type manage the conversion of a service type config to a config file. I'm very sorry about it. > This is not true. Guix is completely capable of doing such things, you > just have to declare it as such. Meaning you need to think of a way to > store the secrets securely, and code the services that will do that. > People have already done this for Nix and > someone has tried to do something similar for Guix: > https://github.com/fishinthecalculator/sops-guix > > I would be surprised if Guix channel didn't accept changes to services > that would make something like that easier, like being able to use files > in the service configurations rather than using config snippets in Guix. I would love to send patches. But I visibly need to learn more about how everything work before. PS: If a service-type store a file in the store and I run the command `guix publish', does the file is readable from another computer as the store is shared ? Have a nice day.
signature.asc
Description: PGP signature
