You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Thibaut Girka ba4521b175 Move compose box options to their own page 6 years ago
.circleci
.github
app Move compose box options to their own page 6 years ago
bin Add improved CLI interface for removing remote media (#8411) 6 years ago
config Add manifest_src to CSP 6 years ago
db Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
docs
lib Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
streaming Add health endpoint to streaming API (#8441) 6 years ago
vendor/assets
.babelrc
.buildpacks Add ffmpeg buildpack for scalingo (#8500) 6 years ago
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox Rename S3_CLOUDFRONT_HOST to S3_ALIAS_HOST. (#8423) 6 years ago
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
.env.test
.env.vagrant
.eslintignore
.eslintrc.yml
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml Fix low-hanging rubocop gripes (#8458) 6 years ago
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
LICENSE
Procfile
Procfile.dev
README.md Fix CI badge, as we have switched from Travis to CircleCI 6 years ago
Rakefile
Vagrantfile
app.json
boxfile.yml
config.ru
docker-compose.yml Update docker config and move some workers to different queues (#8345) 6 years ago
jest.config.js
package.json Add notification badge to favicon 6 years ago
priv-config
scalingo.json Add ffmpeg buildpack for scalingo (#8500) 6 years ago
stack-fix.c
yarn.lock Add notification badge to favicon 6 years ago

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?