Somewhat experimental and sporadically maintained fork of a fork of a fork of Mastodon
Find a file
2018-08-11 15:28:06 +02:00
.circleci Use workspace instead of caching for built assets 2018-07-30 22:25:22 +02:00
.github
app Implement public profile endorsements in glitch-soc 2018-08-10 16:25:46 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-08-10 16:22:31 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2018-08-10 16:22:31 +02:00
docs
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-08-01 00:18:13 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-08-10 16:22:31 +02:00
streaming
vendor/assets
.babelrc
.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
boxfile.yml
Capfile
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
docker-compose.yml Update docker-compose to cope with build-time assets (#8156) 2018-08-09 22:37:48 +02:00
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2018-07-16 14:50:42 +02:00
Gemfile
Gemfile.lock
jest.config.js
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2018-08-01 00:18:13 +02:00
priv-config
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
stack-fix.c
Vagrantfile Merge branch 'master' into glitch-soc/merge-upstream 2018-08-01 22:20:25 +02:00
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-08-01 00:18:13 +02:00

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?