I have a gitea 1.15.3 instance that I will pay attention to in short bursts as projects require, but otherwise I do not wish it to become a repository for random data uploaded from the Internet without my knowledge. What I would like is for new users to be locked down pending some sort of admin moderation to “unlock” them.
To that end, I put the following in its
[service] REGISTER_EMAIL_CONFIRM = false REGISTER_MANUAL_CONFIRM = true ENABLE_NOTIFY_MAIL = false DISABLE_REGISTRATION = false ALLOW_ONLY_EXTERNAL_REGISTRATION = false ENABLE_CAPTCHA = false REQUIRE_SIGNIN_VIEW = false DEFAULT_KEEP_EMAIL_PRIVATE = true DEFAULT_ALLOW_CREATE_ORGANIZATION = true DEFAULT_ENABLE_TIMETRACKING = true NO_REPLY_ADDRESS = noreply.example.org
I was led to understand that
REGISTER_MANUAL_CONFIRM might be what I was looking for, and that it was incompatible with
REGISTER_EMAIL_CONFIRM. However, it seems that account creation is completed via e-mail, and the created accounts are automatically marked as “Activated” in the User Admin tab without my taking any administrative action.
I could just disable account creation, but I do like contributors signing up when I already know them. I don’t just want a brick wall: I want some control.
I suspect that I may be misunderstanding the very short descriptions of these configuration settings in the documentation. Is there a better way to accomplish what I am trying to do?