(Multiple config files doesn't mean multiple processes. Daemon mode is the
only way to get a separate process per site.)
On Sunday, April 19, 2015, Joe wrote:
> @Florian What do you mean the projects are in the same python process?
>
> This is a standard implementation of the sites framework abo
Try it without setdefault or use daemon mode :)
The "standard" configuration has this exact problem, which there's a
warning in the docs and why daemon mode is recommended.
On Sunday, April 19, 2015, Joe wrote:
> @Florian What do you mean the projects are in the same python process?
>
> This is
On Sunday, April 19, 2015 at 10:32:47 PM UTC+2, Joe wrote:
>
> @Florian What do you mean the projects are in the same python process?
>
Let me phrase it differently, does it also happen if you run every project
manually using runserver? If no, then this is a configuration bug, please
see the
@Florian What do you mean the projects are in the same python process?
This is a standard implementation of the sites framework above, which leads
me to believe there is a bug in django 1.7
On Sunday, April 19, 2015 at 12:03:44 AM UTC-7, Florian Apolloner wrote:
>
> Hi,
>
> this is certainly
@Collin, this is not the case. As you can see I have 2 different WSGI
files. The contents of them are:
#site1_wsgi.py
import os
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "site1_settings")
from django.core.wsgi import get_wsgi_application
application = get_wsgi_application()
Ahh, yes, that sounds like the warning box here:
https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/modwsgi/#basic-configuration
On Sunday, 19 April 2015 03:03:44 UTC-4, Florian Apolloner wrote:
>
> Hi,
>
> this is certainly a bug in your code or deployment via mod_wsgi (eg the
> two p
Hi,
this is certainly a bug in your code or deployment via mod_wsgi (eg the two
projects are in the same python process).
Cheers,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe f
I am using django's sites framework. I am calling the site name through a
context processor like below. The problem is that every time the page
loads, it switches between site1 and site2:
def site_info(request):
Site.objects.clear_cache()# i tried with and without this
site = get_current_
