this instance runs on open infrastructure. the code that deploys awful.systems is available here.

right now I've got the following planned for the awful.systems cluster:

• in addition to the current prod lemmy deployment, split off staging and dev. staging will be used to function check infrastructure updates before they hit prod. dev will be used for feature development.
• add a maintenance mode to prod that shuts off the lemmy services and replaces every route with a maintenace page. this will be necessary for big moves like host migrations or storage expansion that'll take the database offline
• make the backend return a damn version so the lemmy apps don't break? I'm guessing this broke because nix deletes .git when pulling sources. this can probably be fixed lazily using keepGit or properly with a patch to lemmy's version detection
• start work on a less janky alternative to lemmy-ui, which will be deployed to dev until it's worth using and hopefully mostly not broken (ima call it lessjank)
• also start work on better moderation tools, implemented in both lemmy-server and lemmy-ui
• probably migrate prod to a bigger hetzner host -- this'll take awful.systems offline for a little bit as I restore the database into the new system
• ~~eventually set up sendgrid? email notifications actually working will probably be beneficial ~~

if you'd like to contribute, contact me. the deployment parts of awful.systems are written in nix, and everything else will be rust