Your self-hosted, globally interconnected microblogging community
Go to file
2019-05-04 19:53:09 +02:00
.circleci
.github
app [Glitch] Fix transition: all 2019-05-04 19:53:09 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 19:15:50 +02:00
log
nanobox
public Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample added documentation into .env.production.sample 2019-04-29 20:52:53 +02:00
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
app.json
Aptfile
AUTHORS.md
babel.config.js
boxfile.yml
Capfile
CHANGELOG.md Bump version to 2.8.1 (#10687) 2019-05-04 00:31:06 +02:00
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
docker-compose.yml Fixed Healthchecks in docker-compose.yml (#10553) 2019-04-23 00:54:26 +02:00
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00
postcss.config.js
priv-config
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
Vagrantfile
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-05-04 16:37:26 +02:00

Mastodon Glitch Edition

Now with automated deploys!

Build Status

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?