A glitchy but lovable microblogging server
Go to file
2019-05-01 22:33:09 +02:00
.circleci
.github
app Add site-wide options to show reblogs and replies in local/public timelines 2019-05-01 22:33:09 +02:00
bin
config Add site-wide options to show reblogs and replies in local/public timelines 2019-05-01 22:33:09 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2019-04-10 09:16:08 +02:00
dist Cache error 410 responses in recommended nginx configuration (#10425) 2019-03-30 03:14:31 +01:00
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-04-22 20:40:04 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-04-10 21:19:21 +02:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample added documentation into .env.production.sample 2019-04-29 20:52:53 +02:00
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
app.json
Aptfile
AUTHORS.md Bump version to 2.8.0rc1 (#10340) 2019-03-30 02:13:42 +01:00
babel.config.js Weblate translations (2019-04-10) (#10545) 2019-04-10 18:17:24 +02:00
boxfile.yml
Capfile
CHANGELOG.md Bump version to 2.8.0 (#10550) 2019-04-10 23:32:08 +02:00
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
docker-compose.yml Fixed Healthchecks in docker-compose.yml (#10553) 2019-04-23 00:54:26 +02:00
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-04-24 15:25:22 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-04-24 15:25:22 +02:00
LICENSE
package.json Fix emoji-mart crashing web UI on search by reverting the upgrade to 2.10.0 (#10413) 2019-03-30 01:41:35 +01:00
postcss.config.js
priv-config
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
Vagrantfile
yarn.lock Fix emoji-mart crashing web UI on search by reverting the upgrade to 2.10.0 (#10413) 2019-03-30 01:41:35 +01: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?