The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
Thibaut Girka f17a61a916 Add basic UI to set list replies setting in glitch-soc 2018-11-28 14:46:07 +01:00
.circleci
…
.github
…
app Add basic UI to set list replies setting in glitch-soc 2018-11-28 14:46:07 +01:00
bin
…
config Merge branch 'master' into glitch-soc/merge-upstream 2018-11-27 15:10:58 +01:00
db Add database support for list show-reply preferences 2018-11-28 14:46:07 +01:00
dist
…
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-11-27 15:10:58 +01:00
log
…
nanobox Update Nginx config for Nanobox apps (#9310) 2018-11-20 22:24:35 +01:00
public
…
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-11-27 13:23:02 +01:00
streaming Only stream local-only toots to logged-in users 2018-11-13 18:55:57 +01:00
vendor/assets
…
.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
…
CHANGELOG.md Bump version to 2.6.2 (#9370) 2018-11-27 13:56:47 +01:00
CODE_OF_CONDUCT.md
…
CONTRIBUTING.md
…
Capfile
…
Dockerfile
…
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2018-11-27 13:23:02 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-11-27 13:23:02 +01:00
LICENSE
…
Procfile
…
Procfile.dev
…
README.md
…
Rakefile
…
Vagrantfile
…
app.json
…
babel.config.js
…
boxfile.yml
…
config.ru
…
docker-compose.yml
…
jest.config.js
…
package.json
…
priv-config
…
scalingo.json
…
stack-fix.c
…
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?