nix configurations used on my server
Find a file
2024-03-19 22:47:33 -07:00
hosts/server oops. dense commit 2024-03-11 17:18:54 -07:00
lib rework lib and some general changes 2024-02-27 23:10:03 -08:00
modules some nginx log and access changes 2024-03-19 22:47:33 -07:00
overlays change permissions 2023-08-22 21:51:48 -07:00
packages change permissions 2023-08-22 21:51:48 -07:00
.editorconfig editorconfig, grafana 2024-02-26 17:02:11 -08:00
default.nix fix import 2024-03-11 17:31:10 -07:00
flake.lock oops. dense commit 2024-03-11 17:18:54 -07:00
flake.nix update more documentation 2024-03-03 22:43:50 -08:00
readme.md oops. dense commit 2024-03-11 17:18:54 -07:00

flake-o-rama

nix flake config! this is just used on my personal server at the moment

please do not use this as a learning resource for nix as i have essentially zero clue what i'm doing

users

this flake is built for a multi-user experience per host, enforced by modules/users.nix, and found in the default.nix file for each host.

as this is a multi-user setup, the dotfiles group will be used for read and write access to the flake

development

to build the system, run sudo nixos-rebuild switch --flake .#server

please periodically run nix flake update to make sure we arent slacking on package versions

before committing, please run nix flake check and make sure everything is ok

todo

  • remove the lua static stuff from nginx + maybe cloudflare ips too + redis
  • per-host architecture selection, atm it is hardcoded to aarch64
  • some weird perl error abt locales when building using doas - keepEnv might fix this
  • move common config such as bootloader and networking settings to default.nix
  • swap back to hardened kernel
  • leverage nixos-hardware
  • somehow add desktop evironments and per-user dotfiles while keeping a multi-user setup - we can always give this up if needed