@dev@microblog.pub Sure! The Apache2 config is fairly simple - certainly no more complex than the nginx one, anyway. I can grab mine as examples when I have some time.

The SCSS theme needs a little more tweaking before it's ready to share, I think - I keep noticing spots I missed styling, lol.

@dev@microblog.pub Also - would there be any interest in an admin settings UI? I find having to shell into the box to update things on a site gets a little tedious after a while. I'll have to do some reading on FastAPI - I've worked mainly in Flask in the past - but I don't think it'd be too hard.

@dev@microblog.pub Oh point, I forgot the multi-process architecture. It'd still be possible, but yeah, way more work. Perhaps I will just start with editing and rebuilding the SCSS/CSS, because that doesn't require process restarts at all.

@dev@microblog.pub Okay, here's the apache configs. They're in two seperate files, because I use Let's Encrypt, so I start with the non-encrypted one and Certbot copies it to the encrypted version, though I think? you can have both in one file.

<VirtualHost *:80>
	ServerName thread.seam.rip

	ServerAdmin webmaster@localhost

ProxyPass "/"  "http://localhost:8000/"
ProxyPassReverse "/"  "http://localhost:8000/"
ProxyPreserveHost On
RewriteEngine on
RewriteCond %{SERVER_NAME} =thread.seam.rip
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

And the SSL one!

<IfModule mod_ssl.c>
<VirtualHost *:443>
	ServerName thread.seam.rip

	ServerAdmin webmaster@localhost

ProxyPass "/"  "http://localhost:8000/"
ProxyPassReverse "/"  "http://localhost:8000/"
ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto "https" 

SSLCertificateFile /etc/letsencrypt/live/thread.seam.rip/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/thread.seam.rip/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>

The ProxyPass, ProxyReverse, ProxyPreserveHeader, and RequestHeader lines are the important ones. The first three you will find in most Apache proxy write-ups but the RequestHeader is a bit of a gotcha, and missing it will cause weird errors with forms (as they try to post to HTTP and not HTTPS). The rewrite and SSL stuff is added by Certbot - you can start with just the HTTP version, minus the rewrite rules, run Certbot, and then get the updated version and SSL version (which needs the header option set)

@darius@friend.camp That always weirded me out when I lived in BC - way more hail than I was used to, and way less lightning (my baseline being 'New England', where we get a lot of summer thunderstorms)

@darius@friend.camp yeah, I saw that and promptly bookmarked it for possible use on Dreamwidth - we're using color picker JS that's at least fifteen years old ahahaha.

@darius@friend.camp the problem with the default color input element is that imolementations vary a LOT in quality by browser OS (for ex, Firefox on Android just gives me a selection of about ten colors to pick from, no other options). I wanna say some of the implementations have a11y issues, too.

(that said I am pro-removing-JS-bloat where possible)