-
Notifications
You must be signed in to change notification settings - Fork 1
Implicit Setup
There is some implicit setup for new devices. It is minimal, but mostly necessary for daily driving a system.
Yes, there are hardcoded paths referenced by the shell. Some may see this as bad design, but I intentionally reference files from the flake for fast wallpaper reloading and deduplication. You need to clone this repository to /home/alec/Projects/flake. Otherwise wallpapers will not appear.
I use a GPG pass store for my passwords. It's very secure and works great in the browser. To set this up for other devices:
Copy your gpg key to a USB drive. Import it: gpg --import <your key>.asc and get its key: gpg --list-secret-keys --keyid-format LONG
Clone the git repo from the homelab: git clone ssh://alec@alechomelab.local/media/pass ~/.password-store
Then just run pass init <your key id from earlier> and you're done! PassFF will read from this automatically and running the integrated system sync command will keep your passwords up-to-date!
If you want to set up a homelab exactly like mine, you first need to write an SD image to the Pi. Head over to the Installation tab on the right for instructions.
You'll need to create a Github Personal Access Token (PAT) on your dashboard. You'll be given a code which you can view once, where you must paste it /home/alec/GithubToken. The GH repository backup service runs daily. The PAT is required to download private repos.
You will also need to create a USB drive with an ext4 filesystem named AlecHomelabDrive. You will need to connect the drive to the Pi using a micro-USB to USB adapter. This is necessary to reduce wear on the SD card - all data is stored here permanently and is removable.
I highly recommend reading through the alechomelab/default.nix file and applying the boot configuration options at the bottom. You can do this by mounting the boot partition and modifying the config.txt and pasting the comment block in.
Coming soon! (I haven't fully set this up on my devices yet, but I plan to do so soon.)
A note about getting AI assistance: Especially with deeper low level config, less intelligent AI models can overcomplicate and bloat the codebase with poor/hacky configuration. If you are going to use AI to modify this flake for you, I highly encourage you to understand the changes its making. AI is a great tool for learning Nix for the first time, but I suggest that you actively learn and understand from what its doing, consult the Nix search and don't be dependent on it.
If it helps to talk to a real person, I am always available to help you with any Nix/NixOS-related questions! (@amazinaxel on Discord)