[Setup] Re: Moving a buildout into production

Raphael Ritz r.ritz at biologie.hu-berlin.de
Wed Aug 27 13:03:04 UTC 2008


Sergey V. wrote:
> 
> 
> Maurits van Rees-3 wrote:
>> If you run bin/buildout then you run the risk of replacing
>> bin/instance and parts/instance.  If the instance is still running
>> while doing this, you end up with a rogue process, preventing you from
>> restarting the instance.  You can always find it with something like
>> 'ps aux' and kill it of course, but I prefer a more gentle approach.
>>
> 
> Well, not stopping a server works 9 times out of 10 (or even 99 out of 100,
> if we take into account that parts/instance is going to be replaced only
> when a new Zope version comes out and that happens not too often). For minor
> updates that's quite safe and if you're unlucky killing the rogue process
> manually may still be faster than waiting for buildout to finish with your
> server down.

As long as you know what you are doing this is just fine.

Depending on the kind of changes you did it might even be sufficient
to run

   bin/buildout -N ...

aka the 'non-update' or 'non-newest' option. This shouldn't touch your
Zope instance under most circumstances.

Raphael


> 
> Having a cache in front of Zope may help in this situation of course.
> 





More information about the Setup mailing list