My configs for both nixos and home manager only machines
Find a file
2024-10-19 22:10:57 +02:00
configs added factorio server to cirrostratus. 2024-10-19 22:10:57 +02:00
hosts added factorio server to cirrostratus. 2024-10-19 22:10:57 +02:00
lib added forgejo config using sqlite. 2024-07-29 15:02:40 -05:00
modules removed work specific clangd formatting. 2024-10-04 08:51:14 +02:00
packages added tailscale to ISOs. 2024-10-01 14:52:14 +02:00
roles broke apart home laptop and desktop config. 2024-06-18 15:06:50 -05:00
templates removed useless and cargo-culted outputs inherrits. 2024-06-10 16:19:36 -05:00
.envrc start of a latepanda config. 2024-05-24 15:23:56 -05:00
.gitignore start of a latepanda config. 2024-05-24 15:23:56 -05:00
flake.lock added grocy server 2024-10-18 22:54:20 +02:00
flake.nix added homepage dashboard. 2024-10-19 18:28:53 +02:00
justfile password hash is now plain file in private repo. 2024-06-05 19:10:12 -05:00
LICENSE Initial commit 2024-03-24 01:38:27 +00:00
README.md made nix-secrets input comment-out-able. 2024-06-12 14:40:04 -05:00

nix-config

My configs for both nixos and home manager only machines

structure

.
├── flake.nix
├── configs
│   ├── home-manager
│   └── nixos
├── hosts
├── modules
│   ├── home-manager
│   └── hostopts.nix
├── roles
│   ├── home-manager
│   └── nixos
└── templates
  • Configs set options and specify programs to be installed. They do not specify their own options, and take effect as soon as they are imported. Generally, a config will be specific to a single program, and possibly optional dependecies of the main program.
  • Hosts define specific hosts. They are the entry point into the system. Each host must import configs/nixos/common.nix in the top level and configs/home-manager/common.nix in the home-manager block. Each host must also define the variables declared in modules/hostopts.nix.
  • Modules are always imported by the respective common.nix. They each have an enable option, and only have effects if enabled.
  • Roles are larger bundles of software and options. They define packages to be installed and may import configurations or enable modules.

Secrets

This repo uses nix-sops for secrets management, with the encrypted secrets being stored in a private repo imported as an input. if the nix-secrets input is commented out, the repo should still build, gracefully degrading to default, non-secret, values.