Or do what I suggested you do in the first place and use mod_wsgi.
Run your main site in embedded mode and your test site in daemon mode.
This will give you the added advantage that to reload test instance,
just touch WSGI script file, no need to restart whole of Apache.
As well as stuff like SE
Hi Graham--
Thanks again for trying to talk me through this stuff. Adding a
different SESSION_COOKIE_NAME to my test site fixed the problem of
having to re-login when switching between my active admin site & my
test admin site. However, the larger problem remains: changes made
to my test site'
On May 25, 9:15 am, Jason <[EMAIL PROTECTED]> wrote:
> Well, actually things are not so bueno. Everything's still working
> fine w/my my main instance, but any changes I make to models on my
> test instance (port 8080, different VirtualHost) are not propagating
> reliably-- or at all-- to the tes
Well, actually things are not so bueno. Everything's still working
fine w/my my main instance, but any changes I make to models on my
test instance (port 8080, different VirtualHost) are not propagating
reliably-- or at all-- to the test site admin screen. Have tried
server restarts, syncdb, etc
And indeed, throwing in a "PythonInterpreter site" in my port 80
VirtualHost, & a PythonInterpreter testsite in my port 8080
VirtualHost solved all my problems. You guys are the best!
On May 21, 5:54 pm, Jason <[EMAIL PROTECTED]> wrote:
> Awesome! Thanks for all the advice, guys. Will try the
Awesome! Thanks for all the advice, guys. Will try the
PythonInterpreter trick & get back to you.
Just FYI, I'd deliberately ignored that part of the documentation
since it specifies:
"If you need to put two Django installations within the same
VirtualHost, you’ll need to take a special precau
On May 22, 9:41 am, Jason <[EMAIL PROTECTED]> wrote:
> On May 21, 4:17 pm, Jashugan <[EMAIL PROTECTED]> wrote:
>
> > On May 21, 4:10 pm, Jason <[EMAIL PROTECTED]> wrote:
>
> > > Hey folks--
>
> > > I'm trying to set up a mirror instance of Django on our webserver,
> > > having grown tired of bring
> > Are you listening on both ports? Check httpd.conf and make sure it has
> > something like this:
>
> > Listen 80
> > Listen 8080
>
> Oh yeah, that's all taken care of. The "test site" is working fine on
> port 8080, separate from the regular port 80 site. My problem is that
> if I change the
On May 21, 4:17 pm, Jashugan <[EMAIL PROTECTED]> wrote:
> On May 21, 4:10 pm, Jason <[EMAIL PROTECTED]> wrote:
>
> > Hey folks--
>
> > I'm trying to set up a mirror instance of Django on our webserver,
> > having grown tired of bringing our whole site down every time I'm
> > debugging new code.
>
On May 21, 4:10 pm, Jason <[EMAIL PROTECTED]> wrote:
> Hey folks--
>
> I'm trying to set up a mirror instance of Django on our webserver,
> having grown tired of bringing our whole site down every time I'm
> debugging new code.
Why aren't you debugging on your local machine?
> I've got an Apac
Hey folks--
I'm trying to set up a mirror instance of Django on our webserver,
having grown tired of bringing our whole site down every time I'm
debugging new code.
I've got an Apache VirtualHost set up on port 8080 that more or less
mirrors our website. And I've installed a separate instance
11 matches
Mail list logo
