Closed marlenekoh closed 8 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.
Created a PR for this change https://github.com/linuxserver/docker-healthchecks/pull/114
The readme isn't wrong, but the init logic was. The linked PR should fix the logic and also updates the readme to clarify setting the CSRF_TRUSTED_ORIGINS as it's not part of the Healthchecks docs.
Is there an existing issue for this?
Current Behavior
From the README
Expected Behavior
However, the behaviour has changed since this commit https://github.com/linuxserver/docker-healthchecks/commit/bd0cb9e6035632f76a01e8d49c40d8cb4d603d18
Please update the readme docs with an example that
CSRF_TRUSTED_ORIGINS
has to be manually set, and that it takes in only a str and not a list (different behaviour from django's CSRF_TRUSTED_ORIGINS)Steps To Reproduce
Works
Does not work
Environment
No response
CPU architecture
x86-64
Docker creation
Container logs