You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
3 years ago | |
---|---|---|
.dockerignore | 3 years ago | |
.eslintrc.js | 3 years ago | |
.gitignore | 3 years ago | |
Dockerfile | 3 years ago | |
README.md | 3 years ago | |
index.js | 3 years ago | |
package-lock.json | 3 years ago | |
package.json | 3 years ago | |
screenshot.png | 3 years ago | |
spam1.png | 3 years ago | |
yarn.lock | 3 years ago |
README.md
Gitea Registration Proxy
Gitea servers have been targeted by a click farm employing human users to create accounts on any server with open registration. These accounts post SEO spam links on thier profiles and sometimes even create repositories.
To combat spam, you can integrate this application with your gitea deployment.
On registration, users are challenged to enter an invite token before they will be allowed to create an account.
Installation
This application only supports the /user/sign_up
endpoint.
Therefore you must configure some sort of front-end reverse proxy server like nginx in order to use it, it can't be used as a front-end for gitea on its own.
- Come up with your own invite token
- It must be a string only containing alphanumeric characters and underscores
- Configure it by setting the
REGPROXY_INVITECODE
environment variable
- Configure this software by setting the
REGPROXY_GITEA
environment variableREGPROXY_GITEA
should be your gitea server's http host and port (not https or a url)
- Run this software
- Tell Nginx to proxy the /user/sign_up path on the gitea domain to hit this software instead of gitea
location /user/sign_up {
proxy_pass http://localhost:8080; # gitea registration proxy port
}
- ???
- Profit!?!? (without spam)