Whitespashe is going to be online/offline a fair bit whilst I migrate away from docker.
Wish me luck everyone!
Well, we're accessible over IPv6. We can't actually talk to other IPv6 instances because of docker-compose nonsense.
Looks like I'm gonna have to start preparing for a migration from docker to a proper VM.
π I was sooooo close.....
Well everyone, I think Whitespashe is now available over IPv6! Does anyone know of any IPv6 only Fedi Instances I can try out?
Is there a method of culling servers that have broken SSL/Excessive timeouts from my instance?
I know `tootctl accounts cull` does something similar, but surely there's a way for mastodon to go: "That instance is dead. I'm cutting all ties with it."
Ugh! Spent 2 days troubleshooting media issues with proxying my s3 media storage for mastodon.
I'm pretty sure I've reverted back to my original config (the one I thought I had issues with), and now it's all okay again!
This weekend has been sent to try me!!!
And now Whitespashe is running on Mastodon 3.2.0!
We're now as up-to-date and efficient as we can reasonably be! Time for a well-earned coffee!
Whitespashe is going offline whilst I bring us up to the most recent version. It's gonna get wild.
Whitespashe.uk is now running on Mastodon Master branch, as the v3.1.2 release can't be built due to a dependency being yanked.
We're bleeding edge guys!
Ugh. I've had to disable full-text searching, as my VM is unable to handle the high memory requirements. Looks like a hardware upgrade is in order soon. π₯
Some memory issues on whitespashe.uk
Rebuilding my elasticsearch db, as it hasn't been running for a couple of months.
Oof. Generating a vanity #tor domain is pretty CPU intensive.
Once that's done, I'll be able to link it to my mastodon node!
Until then: slowness
So, when attempting to use git to manage my Mastodon instance......
I managed to pull the branch that had none of my custom changes, and a completely different docker-compose file.
I then proceeded to bring up my mastodon, screwing with all of my containers.
For whatever reason, it refused to revert container names and volumes, however much I tried.
After eventually switching to the correct branch, and judicious use of 'docker-compose down', everything came back up!
But no luck, as my reverse proxy couldn't see the server.
One nginx restart, and logs started flowing!
We're all back online now, but I blame @mike for giving me well written instructions that I dutifully ignored.
Whitespashe.uk now fully supports 1337-character posts!
Next on the list of admin work, is to get a Gitea instance online, and start mirroring the main mastodon repo. Then, I can have custom patches for this functionality applied on each upgrade.
Extended character limit works! Now I just need to find where to add the correct customisations for Tusky to see it.
Whitespashe is going down whilst I try to extend the posting character limit!
whitespashe.uk has been tuned a little more. With any luck, things should be running a little quicker and should be a little more responsive!
Running a remote account cull on whitespashe.uk
Is it supposed to take ages? Should I be running this on a schedule?
Anyone able to test federation over tor with me?
Also, if I'm using the dockerised tor option by sirboops, how do I go about finding my onion id?
Is anyone else seeing large numbers of random-character usernames registering/attempting to register to mastodon recently? I've got approvals on, but I'm not really happy with the amount of mail that's now being sent from my server....
Friendly Neighbourhood Sysadmin.