[𝖙𝖍𝖗𝖊𝖆𝖙™] on Nostr: Johnny "Jovial Johnny" Peligro 🍅 :nix: npub12lx9h…5mpam i had this problem ...
Johnny "Jovial Johnny" Peligro 🍅 :nix: (npub1sa2…jgrv) npub12lx9hrk3glyf6w4rceguw29qjxlqfvelznkrrlm67c32a7s5u8yqf5mpam (npub12lx…mpam)
i had this problem especially when i got into flake subsystem.
maybe a good starting point is keeping it simple?
tree
common (explains itself)
hardware (useful if lots of common machines)
modules (networking, tailscale, firewall)
services (anything from haas to ntp)
hosts (deployment targets)
secrets (encrypted stuffs)
there's really no right/wrong way to do this stuff. i've seen some repos (mine included at one point) that required a phd to understand them. programmers trying to get cute.
keep in mind it doesn't really matter how you configure it, once your deployment target is loaded and the nix store is hot then organizing is just a matter of well organizing.
if you ever want to pair on stuff let me know.
i had this problem especially when i got into flake subsystem.
maybe a good starting point is keeping it simple?
tree
common (explains itself)
hardware (useful if lots of common machines)
modules (networking, tailscale, firewall)
services (anything from haas to ntp)
hosts (deployment targets)
secrets (encrypted stuffs)
there's really no right/wrong way to do this stuff. i've seen some repos (mine included at one point) that required a phd to understand them. programmers trying to get cute.
keep in mind it doesn't really matter how you configure it, once your deployment target is loaded and the nix store is hot then organizing is just a matter of well organizing.
if you ever want to pair on stuff let me know.