You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.
I'm using gargoyle with nexus. It works perfectly on my development machine. On my production environment (mod-wsgi daemon mode) the condition sets only seem to be getting registered in some of the processes (at least that is what I think is happening - if I open the gargoyle admin page for a switch and keep reloading the page the conditions only show up sometimes).
I've looked into this and don't have an answer yet. We're doing the same approach as django.contrib.admin and many other things so it's a bit confusing. Making _registry a class level variable definitely solves it, but then we have issues with isolation.
I'm using gargoyle with nexus. It works perfectly on my development machine. On my production environment (mod-wsgi daemon mode) the condition sets only seem to be getting registered in some of the processes (at least that is what I think is happening - if I open the gargoyle admin page for a switch and keep reloading the page the conditions only show up sometimes).
I have them both in my INSTALLED APPS
and in my urls.py:
Any ideas on what the problem could be?
The text was updated successfully, but these errors were encountered: