A fairly popular instance also crashed and lost all accounts, toots etc.: https://web.archive.org/web/20180325132625/https://mastodon....
A fairly popular instance also crashed and lost all accounts, toots etc.: https://web.archive.org/web/20180325132625/https://mastodon....
Most Ruby apps have tens to hundreds of dependencies and require a build environment which immediately limits access to a smaller group of developers familiar with Ruby build environments and debugging their way out of any dependency hell. Customization also becomes a problem.
There is also no particular design in Mastodon itself to enable more transparency and prevent any arbitrary behavior and abuse of power.
There's official Docker images that I've been running sucesfully for a while, the deployment of Mastodon is really no different from any other self-hosted app these days.
And just packaging something in Docker does not make the need to understand it go away, what happens when things needs to be configured, when database connections don't work, when things go wrong? You still need to understand the software stack pretty well if you want to run it with any degree of confidence.
Docker is not a requirement, it's an additional deployment option. Sure, having a static binary might be easier, but with Docker is pretty much equivalent, you get one, static download.
Had Mastodon been written in Go, this would not solve the problem of having to know Go if things go seriously wrong and you need to debug the actual software. Do you need C knowledge to run Linux? No, but it is certainly helpful.
For what it's worth, I've never had to touch anything Ruby-related in my several months of running a Mastodon instance.
Rails is performant, but like all languages and frameworks, if you aren't writing good code, it's going to be slow.