Futurist Jim CarrollTotal dogs breakfast of upgrade instructions for latest of Mastodon to v4.3.0
Eager to hear from anyone who has successfully navigated this. It would be good to know what might go off the rails before I attempt.
Silvenga@jimcarroll only needed to update env vars with the new secrets, everything else went smoothly.
yopp@jimcarroll don’t forget to backup both old and new encryption keys! They are used for field level encryption, so if you lose them some data will be lost as well. And if you are planing major version upgrade for Postgres I highly recommend to make a dump before you upgrade.
Mine went sideways,
I suppose because I messed up by running upgrade inside alpine based container, while pg itself is running on Ubuntu based container. musl vs libc broke locale metadata and I had to resort to restoring from the dump
@alex i always do a server level backupo before attempting these things. Not running ina. container but good to know. Tks!
Cenobyte 
@jimcarroll I navigated these on a test server identical to production. Hve not done production. I don't use docker images so can't help if that's your setup. It was a challenging upgrade. Had to build libvips from source as no distro seems to have the latest required. Had to upgrade ruby to 3.5.5 even though it says the minimum is 3.1 or something. Had to upgrade nodejs and figure how to do that.