We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A route to force the rules reload would be useful in order to avoid to restart the web server.
This would be useful for shared hosting or to allow clients to configure their own access list without any knowledge about how a Django App work.
The text was updated successfully, but these errors were encountered:
Hi @muflone!
There is a reload_rules view already that you can use right away.
reload_rules
https://github.com/muccg/django-iprestrict/blob/master/iprestrict/urls.py#L13 https://github.com/muccg/django-iprestrict/blob/master/iprestrict/views.py#L36
The view isn't mentioned in the docs though. I will update the docs soonish.
Sorry, something went wrong.
Docs updated in fork https://github.com/sztamas/django-iprestrict-redux to inform users about the reload_rules URL.
https://django-iprestrict-redux.readthedocs.io/en/latest/changing_and_reloading_rules.html#rules-are-cached
sztamas
No branches or pull requests
A route to force the rules reload would be useful in order to avoid to restart the web server.
This would be useful for shared hosting or to allow clients to configure their own access list without any knowledge about how a Django App work.
The text was updated successfully, but these errors were encountered: