Your experience has been improved, citizen.
Media almost all off of local storage and into cloud blob storage. I've reclaimed almost a TB of storage and offloaded lots of bandwidth.
Status available here, and will be available even when mastodon is down: https://nastatus.com
Status page for the server: https://nastatus.com/status.html
I'm jiggling the server handle a little bit. Things may be a bit slow, but should continue to function. Might be a few #glitches
I am making changes to improve your experience, citizen. Remain calm and buy toilet paper.
For those who want to ping me when there are issues (outside of NAS), my Twitter is: https://twitter.com/theeriner
Automatic update to the latest version of mastodon failed (partially) which is what caused the issue. I've rolled back and will update manually and attempt a fix to prevent this from happening again.
Fixed. Does someone want to build a cachet-monitor config so that I can create a cachet status page and get notifications when there are 500 errors (for authenticated queries?) Current monitoring only alerts me if the un-authenticated main page returns a non-200, which isn't always the case.
* Add new services to NAS
Future NAS services in consideration for deployment:
* Status pages (https://cachethq.io/)
* Pubic infrastructure documentation (https://github.com/rust-lang/mdBook)
* Secure pastebin (https://github.com/sametmax/0bin)
* TOR hidden service
* Resources permitting (low priority):
* free, invitation-only NA VPN (wireguard) server
* potential to host any future No Agenda projects made by producers (in docker containers, using CI+CD)
* Move from current kubernetes cluster to new cluster
The current cluster's operational patterns were created by me over two years ago. I haven't made many operational changes since then, although I did migrate physical machine hosts once. Now two years of development and experimentation down the road, my new system is significantly more mature.
This will be a big deal and will resolve much of the current operational overhead that I am currently burdened with.
* Investigating potential move to Pleroma to reduce server load
Mastodon is a fitting name, as it is as computationally heavy as a mastodon is physically heavy. I would like to move to Pleroma, but don't want to do a "fresh start" if it can be avoided.
If the migration script is not mature enough (or if Pleroma itself is not mature enough), I will put this off.
* Moving static content to S3
Sometime after the new year, I will be moving mastodon's static files to S3. Due to the moderate upload speed and the large volume of data, this will take approximately two days. During this time, I will keep the mastodon server online, but any images uploaded during this period will be lost.
Notice will be given before this migration begins.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!