jan-leila/nix-config
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: jan-leila:c6b129726d772900d459824979697d7d5eb19e99
Branches Tags
jan-leila:main
..
compare: jan-leila:bfe774b74ccf604029f9e2b9870b7eee096069b5
Branches Tags
jan-leila:main

No commits in common. "c6b129726d772900d459824979697d7d5eb19e99" and "bfe774b74ccf604029f9e2b9870b7eee096069b5" have entirely different histories.
c6b129726d ... bfe774b74c

1 changed files with 0 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -53,7 +53,6 @@ nix multi user, multi system, configuration with `sops` secret management, `home
## Tech Debt ## Tech Debt
- [ ] monitor configuration in `~/.config/monitors.xml` should be sym linked to `/run/gdm/.config/monitors.xml` (https://www.reddit.com/r/NixOS/comments/u09cz9/home_manager_create_my_own_symlinks_automatically/) - [ ] monitor configuration in `~/.config/monitors.xml` should be sym linked to `/run/gdm/.config/monitors.xml` (https://www.reddit.com/r/NixOS/comments/u09cz9/home_manager_create_my_own_symlinks_automatically/)
- [ ] migrate away from flakes and move to npins - [ ] migrate away from flakes and move to npins
- [ ] `host.users` should be redone so that we just extend the base `users.users` object. Right now we cant quite do this because we have weird circular dependencies with disko/impermanence (not sure which one) and home manger enabling/disabling users per devices
## Broken things ## Broken things
- [ ] figure out steam vr things? - [ ] figure out steam vr things?
@ -66,7 +65,6 @@ nix multi user, multi system, configuration with `sops` secret management, `home
- [ ] rotate sops encryption keys periodically (and somehow sync between devices?) - [ ] rotate sops encryption keys periodically (and somehow sync between devices?)
- [ ] Secure Boot - https://github.com/nix-community/lanzaboote - [ ] Secure Boot - https://github.com/nix-community/lanzaboote
- [ ] auto turn off on power loss - nut - [ ] auto turn off on power loss - nut
- [ ] every service needs to have its own data pool
- [ ] secondary server with data sync. Maybe a Pi with a usb hdd enclosure and use rtcwake to only turn on once a week to sync data over tailscale with connection initiated from pi's side. We could probably put this at LZ. Hoping for it to draw only like $1 of power a month. Initial sync should probably be done here before we move it over because that will take a while. Data should be encrypted so that devices doesn't have access to it. Project will prob cost like $1800 - [ ] secondary server with data sync. Maybe a Pi with a usb hdd enclosure and use rtcwake to only turn on once a week to sync data over tailscale with connection initiated from pi's side. We could probably put this at LZ. Hoping for it to draw only like $1 of power a month. Initial sync should probably be done here before we move it over because that will take a while. Data should be encrypted so that devices doesn't have access to it. Project will prob cost like $1800
## Data Access ## Data Access
@ -76,7 +74,6 @@ nix multi user, multi system, configuration with `sops` secret management, `home
- [ ] figure out why syncthing and jellyfins permissions don't propagate downwards - [ ] figure out why syncthing and jellyfins permissions don't propagate downwards
- [ ] make radarr, sonarr, and bazarr accessible over vpn - [ ] make radarr, sonarr, and bazarr accessible over vpn
- [ ] move searx, home-assistant, actual, vikunja, jellyfin, paperless, and immich to only be accessible via vpn - [ ] move searx, home-assistant, actual, vikunja, jellyfin, paperless, and immich to only be accessible via vpn
- [ ] FreeIPA/SSSD/LDAP/Kerberos to manage uid and gid's
## Services ## Services
- [ ] vikunja service for project management - [ ] vikunja service for project management