-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
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
Don't overwrite DJANGO_SETTINGS_MODULE #279
Conversation
When deploying praktomat via git changes to the file /src/settings/local.py might cause merge conflicts. A possible solution to this is to configure the settings file in the apache config. For instance ``` SetEnv DJANGO_SETTINGS_MODULE settings.local ``` See also KITPraktomatTeam#259
Have you tried with your above changes to run multiple praktomat instances on the same server? |
Yes. |
The unit test code for praktomat.wsgi of commit 600e270 inside pullrequest KITPraktomatTeam#268 didn't "know" changes inside praktomat.wsgi of commit physikerwelt/Praktomat@3c697c0 inside pullrequest KITPraktomatTeam#279 This is a first step for fixing. Lets create a travis run to have a look on travis output.
If I found some information [1],[2],[3],[4] that by running the Django instances in separate processes there can be no possibility of environment variables leaking from one to the other. We could change And consequently [1] http://blog.dscpl.com.au/2012/10/requests-running-in-wrong-django.html |
I created the change and put it into repository via commit ifrh@12182e7 which is part of and is part of pullrequest Bugfix merge marathon feb2022 ... some more beside "Delete duplicate MOD_XSENDFILE_V1_0 setting" #320 concrete parts are here |
With that commit part ifrh@12182e7#diff-7b5d5f52cec25641ba9f79bd9cda4e6804a8dd95f18274d479faffa9f9e50253R26 I repair a bug resulting from a misunderstanding : DJANGO_SETTINGS_MODULE lives as environment variable, but mod_wsgi.process_group is not an environment variable. |
When deploying praktomat via git changes to the file
/src/settings/local.py might cause merge conflicts.
A possible solution to this is to configure
the settings file in the apache config. For instance
See also #259