A glitchy but lovable microblogging server
Go to file
2019-08-08 09:25:00 +02:00
.circleci
.dependabot
.github
app Fix domain block edition in glitch-soc 2019-08-08 09:14:20 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-08-08 08:44:33 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2019-08-08 08:44:33 +02:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2019-08-05 13:13:28 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-08-08 08:44:33 +02:00
streaming Merge branch 'master' into glitch-soc/merge-upstream 2019-07-30 12:22:33 +02:00
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Added max search results var to sample env 2019-07-20 16:39:48 +02:00
.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 Change Dockerfile to bind to 0.0.0.0 instead of docker-compose.yml (#11351) 2019-07-18 20:28:05 +02:00
Dockerfile Change Dockerfile to bind to 0.0.0.0 instead of docker-compose.yml (#11351) 2019-07-18 20:28:05 +02:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-08-07 13:56:48 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-08-07 13:56:48 +02:00
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2019-08-05 13:13:28 +02:00
postcss.config.js
priv-config
Procfile Bind servers to 0.0.0.0 in Procfile (#11378) 2019-07-22 06:16:30 +02:00
Procfile.dev
Rakefile
README.md
scalingo.json
Vagrantfile
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-08-05 13:13:28 +02: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?