A glitchy but lovable microblogging server
Go to file
2018-12-19 20:49:58 +01:00
.circleci
.github
app Restore oops.gif animation for user who have auto_play_gif set 2018-12-19 20:49:58 +01:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-12-19 12:58:49 +01:00
db Merge branch 'master' into glitch-soc/merge-upstream 2018-12-15 10:45:53 +01:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-12-18 16:55:15 +01:00
log
nanobox
public Replace animated oops.gif by a non-animated image 2018-12-19 20:49:58 +01:00
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-12-19 12:58:49 +01:00
streaming
vendor/assets
.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
.yarnclean
app.json
Aptfile
AUTHORS.md
babel.config.js
boxfile.yml
Capfile
CHANGELOG.md
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
docker-compose.yml
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2018-12-18 16:55:15 +01:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2018-12-18 16:55:15 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-12-18 16:55:15 +01:00
jest.config.js
LICENSE
package.json
priv-config
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
stack-fix.c
Vagrantfile
yarn.lock

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?