After watching the slow loading of assets via backblaze, I've now implemented an nginx cache and haproxy wizardry to try and speed stuff up somewhat!
@angristan contributed to my success via his blog post: https://stanislas.blog/2018/05/moving-mastodon-media-files-to-wasabi-object-storage/
After following that, I then stole a load of code from the mastodon docs and https://blog.sentry.io/2017/03/01/dodging-s3-downtime-with-nginx-and-haproxy
Now I've got a fairly resilient media hosting stack!
My hard drives will surely thank me! Backups too!
Ugh. Had so many issues with networking yesterday. I lost internet for a fair part of the day, my VM hosts would not stay clustered or in sync, either!
I had to completely redesign the network connectivity at home and finally for sorted at about 1am today!
Things seem stable now, but yesterday was sent to try me. 😓
Just tried to upgrade the RAM on my server with a shiny new 8GB stick....
Looks like it's DOA. Now I have to send it back to amazon and wait for a new one. My poor ESX server. Looks like another 4 days wait (at least).
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.
Friendly Neighbourhood Sysadmin.
This is a mastodon instance that allows users to share ideas and participate in discussions.
Whitespashe is named after the Admins' first joint coding project, which replaced spaces within a Word document with non-printable characters.
This would preserve readability, but would fool plagiarism detection sites such as Turnitin.
This site was named after this project, as it represents a desire to create whilst simultaneously sticking it to the Man (or in this case, the hellscape that is Twitter).
We have a hidden service frontend running at: http://whtspshcehqg4nj4wqyiopjcfxradop7ujflycxum7wkfivewqt36zyd.onion
Our code of conduct and extended information can be found after the 'Learn More' link below!