dragon.style admin stuff: image migration
Awrite stylish folks, I am going to start fooling around with permanently fixing the "media drive keeps getting filled up" problem today. I think it looks like this should be able to happen while the site keeps running, but there may be a reboot or two involved.
As always, you can keep an eye on @mollypolynomial and/or @egypturnash for any news about serious downtimes.
Awrite stylish dragons, I'm gonna push a couple of minor changes (unbreaking the default masto style, making the 'backwards' style work again, telling apps that our length limit is 7777). I may be able to do this without taking down the instance; as always, if it's down, see what @egypturnash has to say.
Huzzah, @Gargron was able to provide a couple small tweaks and the important realization that I needed to rebuild the whole thing for those tweaks to actually take hold. Migration continues.
ugh, it broke on the same pre-deployment migration as before. Weird that this migration ran fine on my local copy.
https://github.com/tootsuite/mastodon/pull/12095 seems to be a related commit, let's see what happens if I revert that one change... nnnope!
Off to the Discord, where Garg was awake and is looking into it.
Blaagh, a migration is failing to execute and I'm worrying it's because an earlier migration only went halfway or something. Restoring from my old snapshot. START AGAIN.
...and it ran out of disc space AGAIN, right after I decided that if it did I would resize the droplet.
Which of course takes its own chunk of time. "Up to one minute per gig of data used". Which would be up to 80min. I'm gonna set a timer.
hahaha and seconds after tooting that it finished that particular migration task!
There are many more to do on the journey between 2.4.4 and 3.0.1.
>docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate
uh yeah this sure looks like it's gonna take a while.