A glitchy but lovable microblogging server
Go to file
2019-11-07 21:15:22 +01:00
.circleci Change CircleCI config to build assets with NODE_ENV=test 2019-11-07 13:27:36 +01:00
.dependabot
.github
app [Glitch] Minor improvements to poll composing UI 2019-11-07 14:43:07 +01:00
bin
config Fix build with new sass-loader 2019-11-07 14:56:09 +01:00
db
dist
lib
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-11-07 13:43:56 +01:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox Various updates for Nanobox deploys (#11988) 2019-10-02 00:25:25 +02:00
.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
.sass-lint.yml
.slugignore
.yarnclean
app.json
Aptfile
AUTHORS.md
babel.config.js
boxfile.yml
Capfile
CHANGELOG.md
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
crowdin.yml
docker-compose.yml
Dockerfile Dockerfile: put back EXPOSE directive (#12279) 2019-11-04 12:56:21 +01:00
Gemfile
Gemfile.lock
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2019-11-07 13:43:56 +01:00
postcss.config.js
priv-config
Procfile
Procfile.dev
Rakefile
README.md Fix build status link in README.md 2018-09-28 21:18:04 +02:00
scalingo.json
Vagrantfile
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-11-07 13:43:56 +01: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?