A fork of glitch-soc.
 
 
 
 
 
 
Go to file
Spencer Alves 7d2e6429c2 Merge branch 'glitch' into thread-icon 2018-05-31 21:33:16 -07:00
.circleci
.github
app Merge branch 'glitch' into thread-icon 2018-05-31 21:33:16 -07:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
db
docs
lib
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
streaming
vendor/assets
.babelrc
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
.env.test
.env.vagrant
.eslintignore
.eslintrc.yml Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.travis.yml
.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 Remove Puma pidfile before boot if container receives SIGTERM (#7052) 2018-05-25 18:50:31 +02:00
jest.config.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
scalingo.json
stack-fix.c
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00

README.md

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?