The glaceon.social flavour of glitch-soc, a Mastodon fork

Go to file

Claire 1b493c9fee Add optional hCaptcha support Fixes #1649 This requires setting `HCAPTCHA_SECRET_KEY` and `HCAPTCHA_SITE_KEY`, then enabling the admin setting at `/admin/settings/edit#form_admin_settings_captcha_enabled` Subsequently, a hCaptcha widget will be displayed on `/about` and `/auth/sign_up` unless: - the user is already signed-up already - the user has used an invite link - the user has already solved the captcha (and registration failed for another reason) The Content-Security-Policy headers are altered automatically to allow the third-party hCaptcha scripts on `/about` and `/auth/sign_up` following the same rules as above.		2022-01-24 21:22:13 +01:00
.circleci	…
.github	…
app	…
bin	…
chart	…
config	…
db	…
dist	…
lib	…
log	…
nanobox	…
public	…
spec	…
streaming	…
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	…
.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!

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?

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