A glitchy but lovable microblogging server
Go to file
2017-12-17 21:25:18 -06:00
app use list-ul icon in list header and web/lists 2017-12-17 21:25:18 -06:00
bin
config Fixed index in webpack config 2017-12-11 10:45:21 -08:00
db Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-12-07 04:17:14 +00:00
docs
lib Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-12-08 13:17:14 +00:00
log
nanobox
public
spec Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-12-06 20:17:13 +00:00
streaming Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-11-18 06:17:14 +00:00
vendor/assets
.babelrc
.buildpacks
.codeclimate.yml Disable Code Climate maintainability checks (#5798) 2017-11-23 21:38:17 +01:00
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.yml
.foreman
.gitattributes
.gitignore
.gitmodules Rename themes -> flavours ? ? 2017-12-03 23:26:40 -08:00
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.travis.yml Yarn install from Debian package repository (#5899) 2017-12-06 11:42:30 +01:00
.yarnclean
app.json
Aptfile
boxfile.yml
Capfile
CODE_OF_CONDUCT.md update code of conduct email address 2017-11-21 11:01:28 -05:00
CODEOWNERS
config.ru
CONTRIBUTING.md
docker-compose.yml
docker_entrypoint.sh
Dockerfile Update Yarn to version 1.3.2 (#5900) 2017-12-06 11:42:51 +01:00
Gemfile Remove rabl dependency (#5894) 2017-12-06 15:04:49 +09:00
Gemfile.lock Remove rabl dependency (#5894) 2017-12-06 15:04:49 +09:00
ISSUE_TEMPLATE.md
jest.config.js Removed glitch tests 2017-11-17 19:29:17 -08:00
LICENSE
package.json Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-12-03 21:17:13 +00:00
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
Vagrantfile
yarn.lock Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2017-12-03 21:17:13 +00:00

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?