So here's the deal: we all work on this code, and then it runs on dev.glitch.social and anyone who uses that does so absolutely at their own risk. can you dig it?
- You can view documentation for this project at glitch-soc.github.io/docs/.
- And contributing guidelines are available here and here.
This is what's running on https://vulpine.club/, more or less. No warranties, it could destroy everything.
This is a fork of https://github.com/glitch-soc/mastodon (hereafter referred to as "glitchsoc"), which is itself a fork of https://github.com/tootsuite/mastodon ("tootsuite").
See: diff of glitch-soc/mastodon:master and vulpineclub/mastodon:master
Highlights:
- Foxes occur whereever possible
- Docker-centered deployment process
- Native IPv6 for all external-facing interfaces
master: regular merges from glitchsoc/master, hotfixes and features from tootsuite, local modifications and experimental crapstaging: pre-production smoke tests, where I make sure it runs and looks okay and has basic functionality in a Vagrant-encrusted VMproduction: this is what is actually deployed on vulpine.club
The production branch is automatically built on Docker Hub at vulpineclub/mastodon.