Infrastructure as Code for our home servers
Find a file
2024-02-10 22:21:25 +00:00
docker_swarm Update docker_swarm/README.md 2024-02-10 22:21:25 +00:00
docs restructure documentation 2023-12-29 12:51:42 +01:00
nixos remove terraform database 2024-02-08 23:59:12 +01:00
.envrc remove legacy code 2024-02-08 23:53:02 +01:00
.gitignore WIP: nixos-anywhere for virtual machines 2023-11-25 21:00:21 +01:00
bootstrap.sh move age keys to /etc 2024-01-08 20:47:12 +01:00
flake.lock copy microvm config 2024-01-17 21:28:15 +01:00
flake.nix automatically set host name 2024-01-28 14:08:28 +01:00
README.md Update README.md 2024-02-10 22:14:10 +00:00

nixos-servers

Nix definitions to configure our server. Currently, our three main machines and all virtual machines run NixOS!

Acknowledgements

  • deploy-rs: NixOS deploy tool with rollback functionality
  • kubenix: Kubernetes management in Nix (usage planned for the future)
  • disko: declarative disk partitioning
  • agenix: deployment of encrypted secrets to NixOS machines
  • dns.nix: A Nix DSL for defining DNS zones
  • microvm.nix: Declarative virtual machine management in NixOS

Installation

Prerequisites

  1. Install the Nix package manager or NixOS (link)
  2. Enable flake and nix commands (link)
  3. Install Direnv (link)
  4. Allow direnv for this repository: direnv allow

Bootstrapping

We bootstrap our physical server using nixos-anywhere. This reformats the hard disk of the server and installs a fresh NixOS. Additionally, it deploys an age identity, which is later used for decrypting secrets.

⚠️ This will wipe your server completely ⚠️

  1. Make sure your have a Secret service running (such as Keepassxc) that provides the age identity.
  2. Ensure you have root SSH access to the server.
  3. Run nixos-anywhere: ./bootstrap.sh <servername> <hostname>

Deployment

To deploy all servers at once: deploy To deploy only one server: deploy --targets .#<host>

Known bugs

When deploying a new virtiofs share, the error Failed to connect to '<name>.sock': No such file or directory can occur. This seems to be a bug in microvm.nix and I opened a bug report here. A workaround is to deploy the share without deploy-rs's rollback feature enabled:

deploy --targets .#lewis --auto-rollback false --magic-rollback false

Additional documentation