chandlerswift/machine-config
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
machine-config/bert
History
Chandler Swift 690f64ae80
bert: Update README
2024-11-18 22:25:48 -06:00
..
services bert: Add isaacswift.com and isaac user 2024-11-18 19:42:40 -06:00
configuration.nix bert: Add isaacswift.com and isaac user 2024-11-18 19:42:40 -06:00
hardware-configuration.nix Start setting up bert 2024-10-31 01:06:38 -05:00
Makefile Start setting up bert 2024-10-31 01:06:38 -05:00
README.md bert: Update README 2024-11-18 22:25:48 -06:00

README.md

bert

Installation

  1. Install NixOS minimal
  2. ssh-keygen -N "" -f /etc/secrets/initrd/ssh_host_ed25519_key
  3. Enable SSH server and add root SSH key
  4. Deploy updated config with make
  5. Set up Remote Disk Unlocking
    1. mkdir -p /etc/secrets/initrd && ssh-keygen -N "" -f /etc/secrets/initrd/ssh_host_25519_key
  6. Deploy content:
    • websites in /srv
    • factorio world at /var/lib/factorio/saves/default.zip
    • git/forgejo in /var/lib/forgejo
    • navidrome DB/etc in /var/lib/navidrome
  7. Set up Grafana users (log in with default admin/admin; change creds; configure)

Notes on Caddy

Until 2.8 is released with 24.11, Caddy has a pretty limited sense of what content-types should be compressed:

https://github.com/caddyserver/caddy/blob/v2.7.6/modules/caddyhttp/encode/encode.go#L85-L101

Specifically, this doesn't include GeoJSON, which is a bit of a shame for maps.chandlerswift.com. That said, I'll probably be upgrading to 24.11 as soon as it comes out, so in the intervening time I'm just not going to worry about it.

The list was expanded in this PR:

https://github.com/caddyserver/caddy/pull/6081

SD card

With some microSD cards, rebooting consistently leads to a boot loop. I was suspicious that it was all UHS microsd cards (which, these days, is most of 'em) based in part on information in this PR: https://github.com/armbian/build/pull/4824

I currently have a card in there that reliably works, but I'm 90% sure that it's also a UHS card? So I'm now really confused on what's going on. Do I have bad cards? Bad hardware? Bad bootloader? Bad kernel?

Basically, what I've figured out is this: I have two Microcenter branded cards. One works every time. One never works. They contain the same contents (bootloader, kernel, etc). With that in mind, I guess I'm forced to conclude that it must be a difference in the cards. Both cards work fine for every other use, as far as I can tell.

Anyway, I spent a fair bit of time trying to get it to work, but didn't succeed. After all that nonsense, I just found an SD card that happened to work reliably, used that one instead, and called it good enough! 🙃