You could also ask for tips on the modwsgi list which may have a good
solution.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On Fri, Sep 5, 2014 at 3:28 PM, DJ-Tom wrote:
> Well that seems much too complicated just for running variations of the
> same application twice. There all kinds of stuff running on that server and
> adding a proxy to it would be a nightmare to check if everything still
Well that seems much too complicated just for running variations of the
same application twice. There all kinds of stuff running on that server and
adding a proxy to it would be a nightmare to check if everything still
works.
What a pity, Django is such a powerful tool, but lacks easy
On Tue, Sep 2, 2014 at 3:28 PM, DJ-Tom wrote:
>
>
> Am Dienstag, 2. September 2014 13:51:28 UTC+2 schrieb Tom Evans:
>
>>
>> The most obvious and simple solution is to not use Windows.
>
>
> lol - ever heard of the "box of pandora"? :-)
>
> My knowledge of Linux boxes is
Hi Collin,
unfortunately, changing this makes no difference at all.
Thomas
Am Dienstag, 2. September 2014 17:45:37 UTC+2 schrieb Collin Anderson:
>
> setdefault is what's causing your trouble. Change it to an explicit:
>
> os.environ['DJANGO_SETTINGS_MODULE'] = 'app.settings'
>
--
You
*facepalm*... honestly, I did not spot the difference, i believed the line
I had was right!!!
thanks anyways, I will try that tomorrow.
Am Dienstag, 2. September 2014 17:45:37 UTC+2 schrieb Collin Anderson:
>
> setdefault is what's causing your trouble. Change it to an explicit:
>
>
setdefault is what's causing your trouble. Change it to an explicit:
os.environ['DJANGO_SETTINGS_MODULE'] = 'app.settings'
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
Am Dienstag, 2. September 2014 13:51:28 UTC+2 schrieb Tom Evans:
> The most obvious and simple solution is to not use Windows.
>
lol - ever heard of the "box of pandora"? :-)
My knowledge of Linux boxes is very close to zero - so setting up a server
that is not based on Windows would be
Waitress runs fine on Windows; just install with pip.
On Tuesday, 2 September 2014 13:51:28 UTC+2, Tom Evans wrote:
>
> On Tue, Sep 2, 2014 at 12:08 PM, DJ-Tom
> wrote:
> > Most likely the docs refer to this section of wsgi.py:
> >
> >> # We defer to a
On Tue, Sep 2, 2014 at 12:08 PM, DJ-Tom wrote:
> Most likely the docs refer to this section of wsgi.py:
>
>> # We defer to a DJANGO_SETTINGS_MODULE already in the environment. This
>> breaks
>> # if running multiple sites in the same mod_wsgi process. To fix this, use
>> #
Most likely the docs refer to this section of wsgi.py:
# We defer to a DJANGO_SETTINGS_MODULE already in the environment. This
> breaks
> # if running multiple sites in the same mod_wsgi process. To fix this, use
> # mod_wsgi daemon mode with each site in its own daemon process, or use
> #
See the docs on deploying with mod_wsgi:
https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/
If multiple Django sites are run in a single mod_wsgi process, all of them
will use the settings of whichever one happens to run first. This can be
solved with a minor edit to wsgi.py
Hi,
I'm currently trying to get the same Django app running twice under
different URLs on the same server.
App 1 ran last year under https://www.sample.com/2013/app and should stay
there for reference purposes.
App 2 should run under https://www.sample.com/2014/app and also should use
a
13 matches
Mail list logo