The glaceon.social flavour of glitch-soc, a Mastodon fork

Go to file

ThibG 58946fef3c Merge pull request #1079 from ThibG/glitch-soc/merge-upstream Merge upstream changes		2019-06-04 17:12:25 +02:00
.circleci	…
.dependabot	Add Dependabot config (#10876 )	2019-05-29 09:00:51 +03:00
.github	…
app	[Glitch] Fix profile picture preview	2019-06-03 20:20:33 +02:00
bin	…
config	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +02:00
db	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +02:00
dist	…
lib	…
log	…
nanobox	…
public	…
spec	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +02:00
streaming	…
vendor	…
.buildpacks	…
.codeclimate.yml	…
.dockerignore	…
.editorconfig	…
.env.nanobox	…
.env.production.sample	Add audio length var to env sample	2019-06-03 16:16:21 +02:00
.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	…
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +02:00
Gemfile.lock	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +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 remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +02:00
postcss.config.js	…
priv-config	…
scalingo.json	…
yarn.lock	Merge remote-tracking branch 'upstream/master' into glitch-soc/merge-upstream	2019-06-03 14:54:30 +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.