Jenkins d75a6054a0 Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master		7 years ago
.github	…
app	Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master	7 years ago
bin	…
config	Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master	7 years ago
db	…
docs	…
lib	Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master	7 years ago
log	…
nanobox	…
public	Merge remote-tracking branch 'origin/master' into merge-upstream	7 years ago
spec	…
streaming	…
vendor/assets	…
.babelrc	…
.buildpacks	…
.codeclimate.yml	…
.dockerignore	…
.editorconfig	…
.env.nanobox	…
.env.production.sample	…
.env.test	…
.env.vagrant	…
.eslintignore	…
.eslintrc.yml	…
.foreman	…
.gitattributes	…
.gitignore	…
.gitmodules	…
.haml-lint.yml	…
.nanoignore	…
.nvmrc	…
.postcssrc.yml	…
.profile	…
.rspec	…
.rubocop.yml	…
.ruby-version	…
.scss-lint.yml	…
.slugignore	…
.travis.yml	Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master	7 years ago
.yarnclean	…
AUTHORS.md	…
Aptfile	…
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	…
Gemfile.lock	…
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
Rakefile	…
Vagrantfile	…
app.json	…
boxfile.yml	…
config.ru	…
docker-compose.yml	…
jest.config.js	…
package.json	…
scalingo.json	…
stack-fix.c	…
yarn.lock	…

README.md

Mastodon Glitch Edition

Now with automated deploys!

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.