Aly Raffauf
366179e3d0
Some checks are pending
git-mirror / gitlab-sync (push) Waiting to run
nix-build / default-build (push) Waiting to run
nix-build / fallarbor-build (push) Waiting to run
nix-build / lavaridge-build (push) Waiting to run
nix-build / mauville-build (push) Waiting to run
nix-build / petalburg-build (push) Waiting to run
nix-build / rustboro-build (push) Waiting to run
nix-check / fmt-check (push) Waiting to run
nix-check / eval-check (push) Waiting to run
|
||
---|---|---|
.. | ||
common | ||
fallarbor | ||
lavaridge | ||
mauville | ||
petalburg | ||
rustboro | ||
README.md |
Hosts
Overview
Host-specific configuration + common modules that aren't better expressed as options & flake outputs. All hosts are configured with agenix, disko, and nixhw.
Automatic Updates
These hosts update themselves automatically, once a day, by rebuilding from one of two sources: directly from this repository's master branch or from FlakeHub. This can be adjusted by overriding the value of config.environment.variables.FLAKE
.
FlakeHub allows semantic versioning, which means that these hosts build from the lattest tag published to FlakeHub with format v0.0.0
. I try to follow the semantic versioning 2.0 standard, though this may not always be the case.
You can access the latest tagged commit from this repository with this url: https://flakehub.com/f/alyraffauf/nixcfg/*.tar.gz.
Declarative WiFi Connections
WiFi networks can be configured declaratiely in wifi.nix
using config.networking.networkmanager.ensureProfiles.profiles
, provided by nixpkgs. I also provide helper functions for common wifi security types.
nm2nix can generate nix code for all WiFi networks currently configured in /etc/NetworkManager/system-connections/
and /run/NetworkManager/system-connections
with the following command:
sudo su -c "cd /etc/NetworkManager/system-connections && nix --extra-experimental-features 'nix-command flakes' run github:Janik-Haag/nm2nix | nix --extra-experimental-features 'nix-command flakes' run nixpkgs#nixfmt-rfc-style"
Secrets (passwords, certificates, and identities) are supported, but must be declared and available as variables with agenix. They will be replaced upon activation with envsubst
.
In short,
- Manually configure the WiFi network on one device.
- Export configuration to nix with
nm2nix
. - Add secrets to
secrets/wifi.age
as variables (e.g.MYPSK=1234567890
) - Edit the code generated by
nm2nix
to reference$MYPSK
instead of directly declaring the WPA password. - Commit and push changes.
- Rebuild hosts as required to propogate your new WiFi configuration.
Provisioning New Devices
- Create
hosts/$HOSTNAME/default.nix
and other host-specific nix modules (e.g.disko.nix
,hardware.nix
, andhome.nix
). - Add host to
nixosConfigurations
inflake.nix
. - (OPTIONAL) Generate a
cert.pem
,key.pem
, and device ID for Syncthing withsyncthing -generate=$HOSTNAME
. Find the device ID in the generatedconfig.xml
and add it tonixosModules/services/syncthing/default.nix
, encrypt the cert and key with agenix, and set them as appropriate in the host configuration. - Install NixOS from this flake. Secrets will not be available on first boot without a valid SSH private key.
- On a separate PC, copy the new system's public SSH key (
/etc/ssh/ssh_host_ed25519_key.pub
) to the host configuration (secrets/publicKeys/root_$HOSTNAME.pub
). - Add the new public key to
secrets/secrets.nix
, rekey all secrets withagenix --rekey
, and push your changes to master. - Rebuild the new system from git. Secrets will be automatically decrypted and immediately available in
/run/agenix/
for NixOS and$XDG_RUNTIME_DIR/agenix/
for users. - (OPTIONAL) Generate a new user SSH key and add it to
nixosModules/users/default.nix
in order to enable passwordless logins to other hosts.