I recently had the chance to play around and setup my ionscale server using Nix. During the setup process, I found myself doing most of the configuration of the ionscale using the CLI on the server as opposed to being able to configure them initially using a file. I can see the benefits of being able to dynamically configure for instance tailnets, but as a practice in Nix I very much like to be able to configure my services on the server with a static configuration and forget about it.
I thought other people might also benefit from static configs, so I thought to open up an issue here to hear your thoughts on this. @jsiebens
I'm not a Go dev, but let me know if I can be of any help.
Hi there!
Thanks for the great project!
I recently had the chance to play around and setup my ionscale server using Nix. During the setup process, I found myself doing most of the configuration of the ionscale using the CLI on the server as opposed to being able to configure them initially using a file. I can see the benefits of being able to dynamically configure for instance tailnets, but as a practice in Nix I very much like to be able to configure my services on the server with a static configuration and forget about it.
I thought other people might also benefit from static configs, so I thought to open up an issue here to hear your thoughts on this. @jsiebens
I'm not a Go dev, but let me know if I can be of any help.