From 690f64ae803fc9fc104cb81fcfbc3c51f2d6fc57 Mon Sep 17 00:00:00 2001 From: Chandler Swift Date: Mon, 18 Nov 2024 22:25:48 -0600 Subject: [PATCH] bert: Update README --- bert/README.md | 33 ++++++++++++++++++++++++++++++--- 1 file changed, 30 insertions(+), 3 deletions(-) diff --git a/bert/README.md b/bert/README.md index 5fc22b6..df3d008 100644 --- a/bert/README.md +++ b/bert/README.md @@ -1,13 +1,20 @@ -# Installation +# `bert` + +## Installation 1. Install NixOS minimal 2. `ssh-keygen -N "" -f /etc/secrets/initrd/ssh_host_ed25519_key` 2. Enable SSH server and add root SSH key 3. Deploy updated config with `make` 4. Set up [Remote Disk Unlocking](https://nixos.wiki/wiki/Remote_disk_unlocking) 1. mkdir -p /etc/secrets/initrd && ssh-keygen -N "" -f /etc/secrets/initrd/ssh_host_25519_key -5. Deploy content to web services +5. 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 +6. Set up Grafana users (log in with default admin/admin; change creds; configure) -# Notes on Caddy +## Notes on Caddy Until 2.8 is released with 24.11, Caddy has a pretty limited sense of what content-types should be compressed: @@ -21,3 +28,23 @@ 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! 🙃