I'm having a go at installing #Mastodon, and #gotosocial, comparing them (on 2 different VPS', 2 different domains). The elegance of gotosocial, for installation, is really impressive. 👍

Mastodon has way too many "moving parts" to my liking: it has node.js 🙄 , puma, sidekiq, and redis processes all vying for CPU usage. Despite this little whirlwind of server processes, it *also* wants the webserver, say #nginx to interface with local storage (for its "public" folder), or an S3-style bucket. It has too many tangled dependencies for me to consider it "low-maintenance". It's a "high-maintenance" service - not to be taken lightly. Like I can't just "set it up and forget it".

This is all really unconducive to doing a reverse proxy, where a VPS in the cloud acts as a "simple" reverse proxy, then one runs Mastodon in a lightweight container in one's LAN, like in Incus (and one can still easily use free Let's Encrypt SSL certs).

#OpenSource

Just saying: a base install of #Mastodon is 1.3GB (this includes over 500MB of node.js libraries). That's with one user. And #gotosocial? About 150MB, after its first user.

#OpenSource

@d1 I run a self-hosted single/user #gotosocial instance as well, homelab with dynamic dns, reverse proxy, etc. it is fantastic. No VPS required.