while I don't advocate developer's hitting production .. it happens,
and can make life easier
may I suggest you just set up a sudo command to bounce the server?
I would also make it so you have 2 code-bases and the command would
switch to the 'fresh' one.
ie
the script would do something li
On 08-Jul-06, at 12:37 AM, x0nix wrote:
> Yeah, in ideal world, in HUGE corporation :-)
> In real world, in tiny company we need to make a modification, test it
> and deploy within few hours and as simply as possible.
i am a one man shop - but i follow that procedure.
>
> Of course we do coding
On 07-Jul-06, at 10:52 PM, x0nix wrote:
> Well ... I don't like the idea of every programmer (after every minor
> change) logging in as root to production server.
i dont like it too - but it is far better than having autoreload on
for mod_python on a production server. You have just thrown aw
> Um, you earlier stated that the problem was that you have
> "PythonAutoReload On". That's not on your production server is it?
> Generally, that setting would only be used in a testing environment.
Oh I didn't notice that it should be used only for testing, thanks for
info.
> And do you really
On 7/7/06, x0nix <[EMAIL PROTECTED]> wrote:
>
> Yeah, in ideal world, in HUGE corporation :-)
> In real world, in tiny company we need to make a modification, test it
> and deploy within few hours and as simply as possible.
>
> Of course we do coding 'n testing on other machine, but restart apache
I found this message by Graham Dumpleton where he explains the problem:
http://www.modpython.org/pipermail/mod_python/2006-January/020079.html
I belive this is the explanation:
> When you see what you expect, it is because the request was handled by a
> different Apache child process which had n
Glenn Tenney napsal:
> On Fri, Jul 07, 2006 at 10:22:12AM -0700, x0nix wrote:
> > Well ... I don't like the idea of every programmer (after every minor
> > change) logging in as root to production server.
>
> You shouldn't have your programmers logging in to a production server
> to do testing eve
On Fri, Jul 07, 2006 at 10:22:12AM -0700, x0nix wrote:
> Well ... I don't like the idea of every programmer (after every minor
> change) logging in as root to production server.
You shouldn't have your programmers logging in to a production server
to do testing even if there were no issues about
Kenneth Gonsalves napsal:
> On 07-Jul-06, at 9:19 PM, x0nix wrote:
>
> > After apache restart everything is ok (until I make another change in
> > my code)
>
> that has happened to me at times - my solution is: always restart
> apache on changes - no big deal, keep a terminal for this and press
>
On 07-Jul-06, at 9:19 PM, x0nix wrote:
> After apache restart everything is ok (until I make another change in
> my code)
that has happened to me at times - my solution is: always restart
apache on changes - no big deal, keep a terminal for this and press
up arrow and enter
--
regards
kg
Only one mod_python running (but I intend to run more than one - is it
going to be a problem?).
After apache restart everything is ok (until I make another change in
my code).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 07-Jul-06, at 5:47 PM, x0nix wrote:
> I am trying to use Django with mod_python and I am experiencing
> strange
> auto-reload behavior. When I make any changes in my project, it seems,
> that server shows random "version" of that page since last apache
> restart.
do you have more than one
Hi folks,
I am trying to use Django with mod_python and I am experiencing strange
auto-reload behavior. When I make any changes in my project, it seems,
that server shows random "version" of that page since last apache
restart.
In apache config I've PythonAutoReload On.
Any ideas, similar exper
13 matches
Mail list logo
