Treehouse Mastodon git tree

Go to file

David Yip 19826774f0 keyword mutes: also check spoiler (CW) text and reblogged statuses.		2017-10-22 00:38:53 -05:00
app	keyword mutes: also check spoiler (CW) text and reblogged statuses.	2017-10-22 00:38:53 -05:00
bin	…
config	Fill in create, edit, update, and destroy for keyword mutes interface.	2017-10-21 14:54:36 -05:00
db	Move KeywordMute into Glitch namespace.	2017-10-21 14:54:36 -05:00
docs	…
lib	Merge tag 'v2.0.0' into gs-master	2017-10-18 11:52:04 -05:00
log	…
nanobox	…
public	Merge tag 'v2.0.0rc2' into gs-master	2017-10-12 04:22:59 -05:00
spec	keyword mutes: also check spoiler (CW) text and reblogged statuses.	2017-10-22 00:38:53 -05:00
streaming	use-DB_NAME-in-development (#5430 )	2017-10-17 11:45:37 +02:00
vendor/assets	…
.babelrc	…
.buildpacks	…
.codeclimate.yml	…
.dockerignore	…
.editorconfig	…
.env.nanobox	…
.env.production.sample	…
.env.test	…
.env.vagrant	…
.eslintignore	…
.eslintrc.yml	Enable ESLint rules import/* (#5414 )	2017-10-16 11:12:09 +02:00
.foreman	…
.gitattributes	…
.gitignore	…
.haml-lint.yml	…
.nanoignore	…
.nvmrc	…
.postcssrc.yml	…
.profile	…
.rspec	…
.rubocop.yml	…
.ruby-version	…
.scss-lint.yml	…
.slugignore	…
.travis.yml	Run `i18n-tasks checked-normalized` in Travis CI (#5443 )	2017-10-18 11:57:02 +02:00
.yarnclean	…
Aptfile	…
CODEOWNERS	+ me for Dutch (#5349 )	2017-10-12 19:07:35 +09:00
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	…
Gemfile.lock	Close connection when succeeded posting (#5390 )	2017-10-14 14:38:57 +02:00
ISSUE_TEMPLATE.md	…
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
Rakefile	…
Vagrantfile	…
app.json	…
boxfile.yml	…
config.ru	…
docker-compose.yml	…
docker_entrypoint.sh	…
jest.config.js	Enable coverage for Jest (#5442 )	2017-10-18 11:39:36 +02:00
package.json	Merge tag 'v2.0.0' into gs-master	2017-10-18 11:52:04 -05:00
scalingo.json	…
yarn.lock	Merge remote-tracking branch 'upstream/master' into gs-master	2017-10-16 09:23:59 -05:00

README.md

Mastodon Glitch Edition

Now with automated deploys!

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?

You can view documentation for this project at glitch-soc.github.io/docs/.
And contributing guidelines are available here and here.