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 7c20530fb7 Fix embedded player 4 years ago
.circleci Set bundle config in local file, and set path (#14351) 4 years ago
.github
app Fix embedded player 4 years ago
bin
chart helm: bump default image tag to v3.2.0 (#14476) 4 years ago
config Merge branch 'master' into glitch-soc/master 4 years ago
db
dist
lib Merge branch 'master' into glitch-soc/master 4 years ago
log
nanobox
public
spec Add tests for direct message assertions 4 years ago
streaming Merge branch 'master' into glitch-soc/master 4 years ago
vendor
.buildpacks Remove nodejs buildpack from buildpacks (#14364) 4 years ago
.codeclimate.yml Bump eslint from 6.8.0 to 7.5.0 (#14454) 4 years ago
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
.env.test
.env.vagrant
.eslintignore
.eslintrc.js Enable promise/catch-or-return allowFinally (#14289) 4 years ago
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml Fix rubocop warning (#14288) 4 years ago
.ruby-version
.sass-lint.yml
.slugignore
.yarnclean
AUTHORS.md Update translators (#14374) 4 years ago
Aptfile
CHANGELOG.md Bump version to 3.2.0 (#14395) 4 years ago
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
SECURITY.md
Vagrantfile
app.json Stop using heroku-buildpack-nodejs (#14341) 4 years ago
babel.config.js
boxfile.yml
config.ru
crowdin.yml
docker-compose.yml
ide-helper.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
postcss.config.js
priv-config
scalingo.json
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 4 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?