A fork of glitch-soc.

Go to file

Thibaut Girka 60addb14ce [Glitch] Change icon for domain blocks Port `fa04945365` to glitch-soc		2018-05-27 20:40:58 +02:00
.circleci	…
.github	…
app	[Glitch] Change icon for domain blocks	2018-05-27 20:40:58 +02:00
bin	…
config	Merge branch 'master' into glitch-soc/merge-upstream	2018-05-27 13:20:15 +02:00
db	Merge branch 'master' into glitch-soc/merge	2018-05-14 20:51:50 +02:00
docs	…
lib	Merge branch 'master' into glitch-soc/merge-upstream	2018-05-23 16:05:19 +02:00
log	…
nanobox	…
public	…
spec	Merge branch 'master' into glitch-soc/merge-upstream	2018-05-23 16:05:19 +02:00
streaming	Add media timeline (#6631 )	2018-05-21 12:43:38 +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	…
.travis.yml	ci: Hack around a Travis condition, I guess	2018-05-18 09:51:00 -05:00
.yarnclean	…
AUTHORS.md	…
Aptfile	…
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	Merge branch 'master' into glitch-soc/merge-upstream	2018-05-19 22:41:10 +02:00
Gemfile.lock	Merge branch 'master' into glitch-soc/merge-upstream	2018-05-19 22:41:10 +02:00
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
Rakefile	…
Vagrantfile	…
app.json	…
boxfile.yml	…
config.ru	…
docker-compose.yml	Remove Puma pidfile before boot if container receives SIGTERM (#7052 )	2018-05-25 18:50:31 +02:00
jest.config.js	…
package.json	…
scalingo.json	…
stack-fix.c	…
yarn.lock	…

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.