A fork of glitch-soc.
 
 
 
 
 
 
Go to file
Claire f23f784f18 Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
.circleci
.devcontainer Format JSON and YAML using Prettier (#17823) 2022-03-21 04:46:11 +01:00
.github
app Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
bin
chart
config Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
db Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
dist
lib Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
log Initial commit 2016-02-20 22:53:20 +01:00
nanobox Resync Nanobox files with the 2.9.0 release (#11083) 2019-06-14 14:52:31 +02:00
public
spec Merge branch 'main' into glitch-soc/merge-upstream 2022-04-28 18:16:42 +02:00
streaming Merge branch 'main' into glitch-soc/merge-upstream 2022-04-25 17:09:32 +02:00
vendor
.buildpacks
.codeclimate.yml
.deepsource.toml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.prettierignore
.prettierrc.js
.profile
.rspec
.rubocop.yml
.ruby-version
.sass-lint.yml
.slugignore
.yarnclean
AUTHORS.md
Aptfile
CHANGELOG.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
FEDERATION.md
Gemfile
Gemfile.lock
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
SECURITY.md
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
crowdin.yml
docker-compose.yml
ide-helper.js
package.json
postcss.config.js
priv-config
scalingo.json
yarn.lock

README.md

Mastodon Glitch Edition

Now with automated deploys!

Build Status Code Climate

So here's the deal: we all work on this code, and anyone who uses that does so absolutely at their own risk. can you dig it?