The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
ThibG 5ccd011cc3
Merge pull request #1161 from ThibG/glitch-soc/cherry-pick-upstream
Cherry pick changes from upstream
2019-07-15 01:04:31 +02:00
.circleci
…
.dependabot
…
.github
…
app Change the retry limit in error of web push notification (#11292) 2019-07-15 00:48:50 +02:00
bin
…
config Re-add route for direct timeline 2019-07-07 14:12:41 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2019-06-28 21:36:50 +02:00
dist
…
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-06-28 21:36:50 +02:00
log
…
nanobox
…
public
…
spec Merge commit 'c07cca4727041ea5a5721acbc603d4bfb45a15a6' into glitch-soc/merge-upstream 2019-07-07 13:49:31 +02:00
streaming
…
vendor
…
.buildpacks
…
.codeclimate.yml
…
.dockerignore
…
.editorconfig
…
.env.nanobox
…
.env.production.sample Change .env.production.sample to specify that MAX_VIDEO_SIZE also applies to audio files 2019-06-24 16:27:10 +02:00
.env.test
…
.env.vagrant
…
.eslintignore
…
.eslintrc.js
…
.foreman
…
.gitattributes
…
.gitignore
…
.gitmodules
…
.haml-lint.yml
…
.nanoignore
…
.nvmrc
…
.profile
…
.rspec
…
.rubocop.yml
…
.ruby-version
…
.sass-lint.yml
…
.slugignore
…
.yarnclean
…
AUTHORS.md
…
Aptfile
…
CHANGELOG.md Fix unconverted PRs in the changelog (#11155) 2019-06-22 18:13:52 +02:00
CODE_OF_CONDUCT.md
…
CONTRIBUTING.md
…
Capfile
…
Dockerfile
…
Gemfile Bump rubocop-rails from 2.0.1 to 2.2.0 (#11257) 2019-07-15 00:48:50 +02:00
Gemfile.lock Bump rubocop-rails from 2.0.1 to 2.2.0 (#11257) 2019-07-15 00:48:50 +02:00
LICENSE
…
Procfile
…
Procfile.dev
…
README.md
…
Rakefile
…
Vagrantfile
…
app.json
…
babel.config.js New Crowdin translations (#11077) 2019-06-18 22:58:18 +02:00
boxfile.yml
…
config.ru
…
crowdin.yml
…
docker-compose.yml
…
package.json [Security] Bump lodash from 4.17.11 to 4.17.13 (#11287) 2019-07-15 00:48:50 +02:00
postcss.config.js
…
priv-config
…
scalingo.json
…
yarn.lock Bump handlebars from 4.1.0 to 4.1.2 (#11293) 2019-07-15 00:48:50 +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?