Skip to content

Latest commit

 

History

History
72 lines (52 loc) · 4.04 KB

File metadata and controls

72 lines (52 loc) · 4.04 KB

bphenriques's fleet

Nix Flakes selfhost-nix NixOS Install License: MIT

Hi! 👋 This is how I manage my fleet with NixOS, including a self-hosted homelab running many services with SSO, a reverse proxy, monitoring, and automated off-site encrypted backups (see selfhost-nix and compute's architecture). I hope this helps you!

Hosts

Host Platform Description
compute NixOS Homelab using my selfhost-nix flake
laptop NixOS Personal workstation
inky Raspberry Pi Raspberry Pi Zero 2W connected to Inky Impression and speakers

Nix Stack

Layout:

  • hosts/: per-host configurations (hardware, services, users)
  • modules/: personal NixOS/home-manager modules (the selfhost.* framework lives in selfhost-nix)
  • profiles/: shared opinionated configuration that sets standard options (imported by hosts)
  • packages/: custom packages and scripts
  • lib/: custom helpers and builders
  • apps/: runnable scripts (installation, post-install)

Key dependencies:

  • disko for declarative disk partitioning
  • stylix for consistent theming
  • sops-nix for secrets
  • nixos-anywhere for remote installations
  • selfhost-nix that abstracts common concerns around self-hosting (Reverse Proxy, OIDC, and Secrets)
  • dotfiles-private to store private information (SOPS secrets, personal information, and wallpapers)

Not using flake-utils or impermanence intentionally.

Note

This won't build as-is as it depends on dotfiles-private. Let me know if you need help!

dot cli

Using a personal wrapper to manage both local and remote machines called dot:

dot . s              # build, preview changes, and apply to the current host
dot . b              # build and preview changes without applying
dot . u              # update flake inputs
dot . c              # show changelog between last two local profiles
dot compute s        # deploy to the compute host remotely
dot compute c        # show changelog for the compute host

AI Disclaimer

AI was used from January 2026 onwards, starting with the compute host to learn and iterate faster. I drive the architecture, review and own every line.

Acknowledgements

Thanks to everyone sharing dotfiles, maintaining the Arch Wiki and NixOS Wiki, and helping in the NixOS community.