palo/nixos-config
palo/nixos-config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nixos-config/components
History
Ingolf Wagner 4d76f96a7b
🔧 make forgejo-runner work with docker
2025-02-07 01:05:56 +13:00
..
gui ✨ configure browser plugins 2025-01-22 06:45:22 +13:00
media nix fmt 2024-08-29 08:26:04 +07:00
monitor 🐛 fix migration to nixos-telemetry flake on orbi 2024-10-18 09:26:27 +09:00
network 🚧 downsize cores 2024-12-23 08:39:44 +07:00
nixos nix fmt 2024-08-29 08:26:04 +07:00
terminal 🐛 fixing nix flake update 2024-10-23 09:20:19 +09:00
virtualisation 🔧 make forgejo-runner work with docker 2025-02-07 01:05:56 +13:00
chaospott.nix nix fmt 2024-08-29 08:26:04 +07:00
default.nix ➕ migrate to nixos-telemetry flake 2024-10-16 23:22:52 +09:00
mainUser.nix 🎨 nix fmt 2024-12-06 21:57:53 +07:00
README.md 🎨 nix fmt 2024-08-29 13:22:51 +07:00
timezone.nix 🔧 change timezone 2025-01-02 21:58:23 +13:00
yubikey.nix nix fmt 2024-08-29 08:26:04 +07:00

README.md

components concept

  • components are kinda opinionated.
  • should be project agnostic (e.g.: configure bugwarrior via options but leave specifics out).
  • component.<toplevel>.enabled should usually be the default for all it subcomponents (comonent.<topleve>.<subcomponent>.enabled).
    • But default should make sense here!