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 9e8d776a77 [Glitch] Display verified links in glitch flavor 6 years ago
.circleci
.github
app [Glitch] Display verified links in glitch flavor 6 years ago
bin Upgrade Babel to version 7.0.0 (#5925) 6 years ago
config Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
db
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
vendor/assets
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant update vagrant configs (#8706) 6 years ago
.eslintignore
.eslintrc.yml
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml Move more tasks to tootctl (#8675) 6 years ago
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
AUTHORS.md using mailto scheme in AUTHORS.md (#8663) 6 years ago
Aptfile Adjust Aptfile for Heroku-18 stack (#8588) 6 years ago
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Revert "Updated ruby/node images" (#8712) 6 years ago
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 Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
app.json
babel.config.js Upgrade Babel to version 7.0.0 (#5925) 6 years ago
boxfile.yml
config.ru
docker-compose.yml Misc. typos (#8694) 6 years ago
jest.config.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
priv-config
scalingo.json
stack-fix.c
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 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?