On 08-Jul-06, at 7:50 AM, Iain Duncan wrote:
>
>
>>> Do most shared hosting providers allow one to do that? I would have
>>> thought not
>>
>>
>> not - unless you are on vps hosting with root access, mod_python is
>> not an option unless your provider is kind enough to restart apache
>> reg
>>Do most shared hosting providers allow one to do that? I would have
>>thought not
>
>
> not - unless you are on vps hosting with root access, mod_python is
> not an option unless your provider is kind enough to restart apache
> regularly with a cron job - even that may not be enough
On 08-Jul-06, at 6:00 AM, Iain Duncan wrote:
> Do most shared hosting providers allow one to do that? I would have
> thought not
not - unless you are on vps hosting with root access, mod_python is
not an option unless your provider is kind enough to restart apache
regularly with a cron
On 08-Jul-06, at 1:37 AM, Iain Duncan wrote:
>
> This is my first time using mod_python in production, how do you
> handle
> the need to restart apache?
when you need to restart apache, you restart it
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
--~--~-~--~---
Wade Leftwich wrote:
> Iain Duncan wrote:
>
how do you handle changes on a site which is already online (talking
about changing models and/or views)?
>>>
>>>
>>>I typically maintain a duplicate setup on a testing machine (in my
>>>case, a laptop running Linux) and use that for developme
Iain Duncan wrote:
> >>how do you handle changes on a site which is already online (talking
> >>about changing models and/or views)?
> >
> >
> > I typically maintain a duplicate setup on a testing machine (in my
> > case, a laptop running Linux) and use that for development and
> > testing, then w
>>how do you handle changes on a site which is already online (talking
>>about changing models and/or views)?
>
>
> I typically maintain a duplicate setup on a testing machine (in my
> case, a laptop running Linux) and use that for development and
> testing, then when I know I've got the bugs w
On 7/7/06, patrickk <[EMAIL PROTECTED]> wrote:
> how do you handle changes on a site which is already online (talking
> about changing models and/or views)?
I typically maintain a duplicate setup on a testing machine (in my
case, a laptop running Linux) and use that for development and
testing, t
8 matches
Mail list logo
