Go to file
Thibaut Girka 269edc0e48 Fix CW icon color in local-settings modal 2018-10-09 18:10:54 +02:00
.circleci
.github
app Fix CW icon color in local-settings modal 2018-10-09 18:10:54 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-10-09 12:12:03 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2018-10-08 13:51:33 +02:00
dist Add nginx and systemd templates (#8770) 2018-09-24 16:46:05 +02:00
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-10-08 13:51:33 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-10-08 13:51:33 +02:00
streaming Add conversations API (#8832) 2018-10-07 23:44:58 +02:00
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
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2018-10-08 13:51:33 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-10-08 13:51:33 +02:00
LICENSE
Procfile
Procfile.dev
README.md Fix build status link in README.md 2018-09-28 21:18:04 +02:00
Rakefile
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
docker-compose.yml
jest.config.js
package.json Revert Font Awesome 5 upgrade (#8810) 2018-09-28 02:11:14 +02:00
priv-config
scalingo.json
stack-fix.c
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-10-07 19:47:56 +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?