Short answer: Hell yes.
After completing the full migration and running in production for weeks, I can confidently say GoToSocial is ready for serious use.
Perfect For: ✅
- Self-hosters with limited resources (VPS with 1-2GB RAM? No problem!)
- Single-user or small family instances (works great up to ~50 users based on
Hi all, we’ve noticed that some people who used the dockerlatesttag were already running 0.18.0-rc1 without realizing it. The backport release of 0.17.4 yesterday overwrote thelatesttag (because tobi is a boob), so folks pulling the Docker container again may run into issue.
In order to host Elk yourself you can use the provided Dockerfile to build a container with elk. Be aware, that Elk only loads properly if the connection is done via SSL/TLS. The Docker container itself does not provide any SSL/TLS handling. You’ll have to add this bit yourself. One could put Elk behind popular reverse proxies with SSL Handling like Traefik, NGINX etc.
An alternative to Phanpy, which also works with GoToSocial instances. At least this looks more robust than Phanpy. Gotta deploy one soon.
Edit: Wasn’t able to deploy successfully. Sad.
Browse most recent public posts across the fediverse by hashtag.
This is a great project. Lots of posts I’ve discovered from using this hashtag search. I know the source is on Github, but I wish this is easily selfhostable complete with Docker and compose documentation.
See Github page and blog post.
GoToSocial uses the configured storage backend in order to store media (images, videos, etc) uploaded to the instance by local users, as well as to cache media attached to posts and profiles federated in from remote instances.
GoToSocial total storage space usage currently stands at 3.9GB. If this gets out of hand, I may need to add in the environment variable of the compose.yml file:
GTS_MEDIA_REMOTE_CACHE_DAYS: 2
Mastodon and other Fediverse instance Front end