First of all, thanks for this amazing library. Having an opinionated framework for modules organization helped me tame my configuration as it grew.
Still, I had one tooling/usability issue: while refactoring my configuration I often got lost in the multitude of default.nix files. Before I migrated to this library I used to have hosts configured in configuration.nix, users — in home.nix, which gave me a very helpful optical clue. Also, I frankly missed my old directory structure, where all hosts, both darwin and nixos, resided in a single ./hosts directory.
I made a small change to this lib, which improved usability for me significantly!
My configuration isn't public, but let me illustrate, what kind of configurations are possible with this change:
First of all, thanks for this amazing library. Having an opinionated framework for modules organization helped me tame my configuration as it grew.
Still, I had one tooling/usability issue: while refactoring my configuration I often got lost in the multitude of
default.nix
files. Before I migrated to this library I used to have hosts configured inconfiguration.nix
, users — inhome.nix
, which gave me a very helpful optical clue. Also, I frankly missed my old directory structure, where all hosts, both darwin and nixos, resided in a single./hosts
directory.I made a small change to this lib, which improved usability for me significantly!
My configuration isn't public, but let me illustrate, what kind of configurations are possible with this change:
ezConfigs configuration
Directory structure of my flake (with some nodes omitted for brevity)
I believe this feature may be useful to others, and I'd love to see it accepted upstream.