home/nixos-servers
home/nixos-servers
2
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions
Infrastructure as Code for our home servers
142 commits 3 branches 0 tags 2.2 MiB
Nix 98.7%
Shell 1.3%
Find a file
Pim Kunis f38b9af075 manage vcpus and memory of VMs 
fix kitchenowl connectivity
2024-02-08 23:44:36 +01:00
docs restructure documentation 2023-12-29 12:51:42 +01:00
legacy manage vcpus and memory of VMs 2024-02-08 23:44:36 +01:00
nixos manage vcpus and memory of VMs 2024-02-08 23:44:36 +01:00
.envrc add psql env variables to .envrc 2023-11-25 14:43:37 +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 about microvm bug 2024-02-05 22:50:57 +01:00

README.md

nixos-servers

Nix definitions to configure our physical servers. Currently, our three main servers are all Nixified!

Additional documentation

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