This is my humble flakes-only collection of all and everything needed to set up and maintain all my nixified devices.

• Automation scripts to setup a fresh installation and update the system easily
• nix-on-droid-managed android phone with home-manager
• Generated shell scripts are always linted with shellcheck
• Checks source code with deadnix, statix and nixpkgs-fmt (using nix-formatter-pack)
• Github Actions pipeline for aarch64-linux systems
• Every output is built with Github Actions and pushed to cachix
• Weekly automatic flake input updates committed to master when CI passes

• NixOS-managed
  • DANIELKNB1 (private laptop, WSL2)
  • twopi (Raspberry Pi)
• home-manager-managed
  • maiziedemacchiato with Arch Linux (private laptop)
• nix-on-droid-managed
  • sams9

See flake.nix for more information like system.

If any of these systems need to be reinstalled, you can run:

$ nix run \
  github:573/nix-config-1/wsl2#setup

Note:

• NixOS-managed systems should be set up like written in the NixOS manual. nix build ".#installer-image" can be used for latest kernel, helpful default config and some pre-installed utilities.

# install nix setup
sh <(curl -L https://nixos.org/nix/install) --no-channel-add --no-modify-profile
. ~/.nix-profile/etc/profile.d/nix.sh
nix run \
  --extra-experimental-features "nix-command flakes" \
  github:573/nix-config-1/wsl2#setup

1. Build image

   nix build ".#rpi-image"

2. Copy (dd) result/sd-image/*.img to sd-card
3. Inject sd-card in raspberry and boot
4. When booted in the new NixOS system, login as tobias and run setup script

Firmware of Raspberry Pi needs to be updated manually on a regular basis with the following steps:

1. Build firmware

   nix build ".#rpi-firmware"

2. Mount /dev/disk/by-label/FIRMWARE
3. Create backup of all files
4. Copy result/* to firmware partition (ensure that old ones are deleted)
5. Unmount and reboot

Go to update-flake-lock. There Use workflow from | Branch: master. When action is finished go to Pull requests, choose the latest Update flake.lock and use the Rebase and merge (The 1 commit from this branch will be rebased and added to the base branch.) approach.

When emacs is modified i. e. packages are changed, there may occur discrepancies i. e. packages missing being noticed at runtime which often is related to so first check the flake input emacs-overlay, might refer to a dated version. Also when updating emacs the aarch64-linux variant needs to be remote-built or binfmt-built and pushed to a cache as its build causes an OOM killer on certain devices.

Observe the recommendations on n-o-ds page for device settings (or directly here).