A fork of glitch-soc.

Go to file

Thibaut Girka cbda1b8b66 Add back description on hover		2019-05-04 20:03:37 +02:00
.circleci	…
.github	…
app	Add back description on hover	2019-05-04 20:03:37 +02:00
bin	…
config	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
db	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
dist	…
lib	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 19:15:50 +02:00
log	…
nanobox	…
public	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
spec	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
streaming	…
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	…
.nvmrc	…
.profile	…
.rspec	…
.rubocop.yml	…
.ruby-version	…
.scss-lint.yml	…
.slugignore	…
.yarnclean	…
AUTHORS.md	…
Aptfile	…
CHANGELOG.md	Bump version to 2.8.1 (#10687 )	2019-05-04 00:31:06 +02:00
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
Gemfile.lock	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
Rakefile	…
Vagrantfile	…
app.json	…
babel.config.js	…
boxfile.yml	…
config.ru	…
docker-compose.yml	…
package.json	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00
postcss.config.js	…
priv-config	…
scalingo.json	…
yarn.lock	Merge branch 'master' into glitch-soc/merge-upstream	2019-05-04 16:37:26 +02:00

README.md

Mastodon Glitch Edition

Now with automated deploys!

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?

You can view documentation for this project at glitch-soc.github.io/docs/.
And contributing guidelines are available here and here.