Hey party people of Fedi, the BSD.Network instance will be moving hosting providers tomorrow. We'll be offline for a number of hours, but will fetch the timeline updates once we return. You don't need to do anything, DNS will be updated and the identification keys will stay the same.
so long, it's time to migrate bsd.network! we'll see you from the new server.
unfortunately we let go of our butts during the bsd.network migration process, and ended up with a corrupted database. Had to delete it and re-migrate without the corruption. Some posts were lost, and we're very sorry about that.
with my posts and the day is good 
the instance is doing fairly well, we let it crunch though lots and lots of queued posts while we slept.
now, we still need to fetch 150k+ posts from remote servers and process those, but the queue runners are running.
all we need to do is keep an eye on the queues and runners, which is very easy 
Hey party people of Fedi. If you're feeling saucy, go into your job queues and restart any "failed" that were aimed at BSD.Network.
Using Mastodon software, it's Sidekiq | Dead | (scroll to bottom) Retry All.
we've fully caught up with all of the queued posts and jobs, so I declare the migration of BSD.Network to be successfully complete.
Happy tooting!
🐘💨
(time to close all of those "research" tabs, xterms, ssh sessions, and notes files)
Not at all concerned about the actual problem. Not at all.
Glad to see us back, but care far more about your stress and sanity during the outage.
A space for Bonfire maintainers and contributors to communicate
