A fork of glitch-soc.
 
 
 
 
 
 
Go to file
Thibaut Girka f3e7634156 Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 17:31:02 +01:00
.circleci
.github
app Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 17:31:02 +01:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-03-08 20:15:57 +01:00
db Fix AddLockVersionToPolls migration (#10200) 2019-03-07 01:50:06 +01:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 17:31:02 +01:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-03-10 16:48:44 +01:00
streaming Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 11:23:50 +01:00
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
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Re-organize Dockerfile to improve incremental builds. (#10212) 2019-03-08 16:12:48 +01:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 17:31:02 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-03-11 17:31:02 +01:00
LICENSE
Procfile
Procfile.dev
README.md
Rakefile Initial commit 2016-02-20 22:53:20 +01:00
Vagrantfile Merge branch 'master' into glitch-soc/merge-upstream 2019-03-10 16:48:44 +01:00
app.json
babel.config.js
boxfile.yml
config.ru
docker-compose.yml
jest.config.js
package.json
postcss.config.js
priv-config
scalingo.json
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?