The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
Thibaut Girka c057aeb76b [Glitch] Add documentation for “p” hotkey
Port ed50c2393a0f12f88f1102f8cf8beca3bf711158 to glitch-soc
2018-07-26 22:19:01 +02:00
.circleci Increase timeout for assets:precompile 2018-07-18 21:20:30 +02:00
.github
app [Glitch] Add documentation for “p” hotkey 2018-07-26 22:19:01 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-07-26 21:22:43 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2018-07-16 14:50:42 +02:00
docs
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-07-16 14:50:42 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-07-16 14:50:42 +02:00
streaming Fix streaming API still using filtered instead of chosen languages (#8009) 2018-07-14 03:59:31 +02:00
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
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2018-07-16 14:50:42 +02:00
Gemfile
Gemfile.lock
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
boxfile.yml
config.ru
docker-compose.yml
jest.config.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 2018-07-17 22:05:25 +02:00
priv-config
scalingo.json
stack-fix.c
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-07-17 22:05:25 +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?