nixos-config
NixOS Fleet Flake for multi-host infrastructure with sops-nix secrets, disko, impermanence, deploy-rs, Tailscale, and CI.
Ficha actualizada 22 sept 2026, 21:55 · upstream 22 sept 2026, 21:45 · release sin release detectada
Qué es nixos-config
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
A single, reproducible NixOS and Home Manager flake for a secure workstation, companion laptop, cloud homeserver, and on-demand remote builder. This is not a generic starter template; it implements working, multi-host personal infrastructure with documented patterns, checks, and operational boundaries. The reusable building blocks are exposed through stable flake outputs while host assemblies remain hardware-bound.
- Secure workstation deployment across multiple devices
- Cloud homeserver management (Vaultwarden/AdGuard)
- On-demand remote builder for development environments
- Companion laptop with NixOS and Home Manager
- Tailscale-connected multi-host infrastructure
- CI/CD pipeline automation via deploy-rs
- Impermanent workstation with explicit persistence on /persist, ensuring state survives reboots while keeping root ephemeral
- Self-hosted observability stack (Grafana, Mimir, Loki, Tempo) configured declaratively with client-side collectors and dead-man's-switch health checks
- Security policy as testable invariants checked via Nix flake tests against CI pipelines
- Single source of truth for fleet metadata through lib/hosts.nix driving Tailscale ACLs, backup policies, and inventory export
- Runtime theming with pre-generated assets ensuring identical colors across rebuilds and runtime switches
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy the flake using `nix develop` or `nix build .#installer-iso`. For production use, consider adding a CI/CD pipeline (e.g., GitHub Actions) to run checks on every commit. Use `nix run .#doctor` before deployment to validate configuration. Host metadata and Tailscale ACLs are managed via lib/hosts.nix; update the registry when hosts change. Backup the flake itself using disko or rsync for fleet recovery.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.