The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
Thibaut Girka 356e9150df Merge branch 'master' into glitch-soc/merge-upstream
Conflicts:
- app/lib/sanitize_config.rb
  Keep our version, we support the tags upstream transforms.
- package.json
- yarn.lock
2019-06-19 18:36:16 +02:00
.circleci
.dependabot
.github
app
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-06-19 18:36:16 +02:00
db
dist
lib
log
nanobox
public
spec
streaming Fix streaming server crashing when updating filters 2019-06-18 16:50:04 +02:00
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore Remove Storybook () 2017-07-27 22:30:27 +02:00
.nvmrc
.profile
.rspec
.rubocop.yml require rubocop-rails in .rubocop.yml () 2019-06-06 12:31:48 +02:00
.ruby-version
.sass-lint.yml
.slugignore Remove Storybook () 2017-07-27 22:30:27 +02:00
.yarnclean
AUTHORS.md
Aptfile
CHANGELOG.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile
Gemfile.lock
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
crowdin.yml
docker-compose.yml
package.json
postcss.config.js
priv-config
scalingo.json
yarn.lock

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?