Closed binarypatrick closed 11 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
A few things
1) why would you NOT see sign-in just because you don't allow registration?
2) I do not see that there is an ENVVAR for - REGISTRATION_OPEN=False
, though it is possible it works. The documented method is to modify local_settings.py (you do mention you see it here)
tl;dr it seems registration_open = false
is working as expected, unless you are implying that users are still able to register (which is not something you have shown.
that all said, even if registration were still open, we support the container, not the application and you would need to seek help from the upstream dev support. Being this as it is, I will close this as something we will not fix, as it is not our place (and it doesn't seem there is anything to fix to begin with)
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
I have been trying to close registration for my local healthchecks instance. I used the
REGISTRATION_OPEN
flag and set it to false, but it does not seem to have an effect.I'll also note I see
REGISTRATION_OPEN = False
inconfig/local_settings.py
too, but I still see the sign in on the landing page.Expected Behavior
No login available
No response
Steps To Reproduce
Use the YAML above run
docker compose up -d --force-recreate
navigate to the IP of the host still see the signupEnvironment
CPU architecture
x86-64
Docker creation