A glitchy but lovable microblogging server
Go to file
2019-02-12 20:29:55 +01:00
.circleci
.github
app Merge pull request #913 from ThibG/glitch-soc/merge-upstream 2019-02-12 20:29:55 +01:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
db Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-01-28 21:14:47 +01:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.js Refactor icons in web UI to use Icon component (#9951) 2019-02-01 00:14:05 +01:00
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
app.json
Aptfile
AUTHORS.md Add translators to AUTHORS.md (#9865) 2019-01-19 22:01:12 +01:00
babel.config.js
boxfile.yml
Capfile
CHANGELOG.md Bump version to 2.7.1 (#9932) 2019-01-28 04:24:12 +01:00
CODE_OF_CONDUCT.md update code of conduct email address 2017-11-21 11:01:28 -05:00
config.ru
CONTRIBUTING.md Merge branch 'master' into glitch-soc/merge-upstream 2019-01-28 21:14:47 +01:00
docker-compose.yml
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-02-10 21:10:09 +01:00
jest.config.js Merge branch 'master' into glitch-soc/merge-upstream 2019-02-01 16:12:20 +01:00
LICENSE
package.json
postcss.config.js
priv-config
Procfile
Procfile.dev
Rakefile
README.md Bumps copyright year in README.md to 2019 (#9939) 2019-01-28 22:57:42 +01:00
scalingo.json
stack-fix.c
Vagrantfile
yarn.lock

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?