depot/modules/xnet/nginx.nix, branch master Unnamed repository; edit this file 'description' to name the repository. http://src.web.4kb.net/depot/atom/modules/xnet/nginx.nix?h=master 2025-04-03T01:59:20Z automate project structure 2025-04-03T01:59:20Z Kleidi Bujari mail@4kb.net 2025-04-03T01:59:20Z urn:sha1:09c2b6de63a6ff35348fcb2c2eb57b974f0a8a52 Push configuration out of flake 2024-12-18T04:03:27Z Kleidi Bujari mail@4kb.net 2024-12-18T04:03:27Z urn:sha1:eb13a9a552f9e50a66faba985521ba8e3483c447 Projects are not necessarily all exported by the system flake, and should freely support other derivations. The new "mod" directory will be used for most projects, and it can be imported by machine configurations. That said, the tooling around flakes is pretty good and will still be used until the dependency is lessened. Finalize working configs and prior to adding secrets 2024-12-10T18:24:51Z Kleidi Bujari mail@4kb.net 2024-12-10T18:24:51Z urn:sha1:f5ed731abbc38d765333b005b9815a5f6d3e59c2 System configurations in a known good state. Secrets still have to be integrated, at this point the nixos-anywhere project will likely handle this to keep the bootstrap completely automatic since it can copy ssh host keys to the host prior to install/activation. This would work nicely with the sops secret module, but a good way to manage host keys for each machine still has to be decided. Cleanup xnet module and add baseline modules 2024-12-02T03:30:26Z Kleidi Bujari mail@4kb.net 2024-12-02T03:30:26Z urn:sha1:f08f3812f40322b6098d75573413ed83f358871f With these changes, the xnet module is useable as a system builder. At this point, it is still undecided whether all configuration will be generalized into this module, rather than keeping mini-modules local to the machine they will run on.