Nix Configurations

Used to deploy m1cr0man.com primarily

Using this repo in your own flakes

Everything in this repo is reusable, you don't have to fork it! All modules are exported under the nixosModules flake output keyed by their path. For example, m1cr0manFlake.nixosModules.sysconfig.zfs.

Secrets using Age, sops and sops-nix

Age is a simple program to encrypt/decrypt files.

sops is an encypted file editor supporting age (like ansible-vault) and manages using multiple keys to encrypt/decrypt.

sops-nix provides a way to load sops encrypted config files into Nix.

Using the VS Code plugin to edit secrets

Simply open one of the files in secrets in VS Code. It will open a temporary decrypted file, and close it when you close the file.

Using the CLI to edit secrets

Type sops secrets/filename.yaml

Adding a new admin key

You can generate one from your SSH key. This is recommended - you are probably already keeping your SSH key safe (right?), so you can regenerate your age key from it if you ever lose it.

# Optional: If your key has a passphrase, copy it and remove the pwd first
# ssh-to-age can't prompt for password.
cp ~/.ssh/id_ed25519 ~/
ssh-keygen -p -N "" -f ~/id_ed25519
ssh-to-age -private-key -i ~/id_ed25519 >  ~/.config/sops/age/keys.txt
age-keygen -y ~/.config/sops/age/keys.txt
# Output is the entry to add to .sops.yml

Adding a new host key

Again, you can use the host's sshd host key to build an age key.

sudo cat /etc/ssh/ssh_host_ed25519_key.pub | ssh-to-age
# Output is the entry to add to .sops.yaml
# Also update relevant secret files
sops updatekeys modules/secrets/shared.yaml
sops updatekeys hosts/$HOSTNAME/secrets.yaml

Operational Guides

Upgrading Postgresql

• Bump the version in the configs and disable all ensure/script code.
  • If you don't disable the ensure lines, you will get the error Only the install user can be defined in the new cluster..
• Stop postgresql.service
• Run pg_upgrade like so:

# Find and export the previous version as OLD_BIN
echo /nix/store/*postgresql-14*/bin
export OLD_BIN=/nix/store/asdiuahdsihfsfd-postgresql-14.11/bin
export NEW_BIN=$(dirname $(readlink $(which psql)))
cd /var/lib/postgresql
systemctl stop postgresql
sudo -su postgres pg_upgrade --old-datadir 14 --new-datadir 16 --old-bindir $OLD_BIN --new-bindir $NEW_BIN --check
# Run again without check mode to do migration
# Some recommendations may be given in the output. Do those too.
sudo -su postgres vacuumdb --all --analyze-in-stages
./delete_old_cluster.sh
rm delete_old_cluster.sh

Tailnet dies

• Run tailscale status on the problematic node.
• Restart headscale to validate it's not a home server issue.
  • This solves "Tailscale could not connect to any relay server.".
• Check logs of tailscaled and restart.
• Ensure firewall allows tailscale0.