A glitchy but lovable microblogging server
Go to file
2020-02-22 23:07:29 +01:00
.circleci Fix Gemfile.lock (#12995) 2020-01-28 18:50:44 +01:00
.dependabot
.github
app Document alt+enter 2020-02-22 23:07:29 +01:00
bin
config Fix ActiveRecord::Migration.check_pending! failing because of duplicate migrations 2020-02-10 20:04:41 +01:00
db
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +01:00
log Initial commit 2016-02-20 22:53:20 +01:00
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +01:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Add environment variable to specify extra data hosts 2020-02-06 12:15:15 +01:00
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore Remove Storybook (#4397) 2017-07-27 22:30:27 +02:00
.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 Bump version to 3.1.1 (#13069) 2020-02-10 02:55:40 +01:00
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
crowdin.yml
docker-compose.yml
Dockerfile Fix non-x64 architectures not being able to build Docker image because of hardcoded Node.js architecture (#13081) 2020-02-16 12:54:57 +01:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +01:00
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +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 Merge branch 'master' into glitch-soc/merge-upstream 2020-02-03 09:22:58 +01:00
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2020-02-19 23:04:18 +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?