chandlerswift/machine-config
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
machine-config/bert
History
Chandler Swift 9e3c4ee13e
bert: Add handle_errors clause to all sites 
It looks like this was CLOSED WONTFIX: How can we _possibly_ know that
upon an error, the developer might want us to send an indication of that
error??!!1! Snark aside (mine and his): it looks like there's not a
great way to enable sane error behavior globally :/

https://caddy.community/t/handling-errors-globally/17174/2

In the future, I should probably make this a snippet or something.
2024-11-12 10:56:03 -06:00
..
services bert: Add handle_errors clause to all sites 2024-11-12 10:56:03 -06:00
configuration.nix bert: Add navidrome 2024-11-12 10:56:03 -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 Start setting up bert 2024-10-31 01:06:38 -05:00

README.md

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 to web services

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