[Setup] Re: What happens if something goes wrong?

[Alexander Limi]

If you're running buildout, Reinout's backup recipe uses repozo, and takes  
care of pretty much everything:

http://vanrees.org/weblog/archive/2008/07/03/easy-backups-with-buildout

— Alexander

On Wed, 02 Jul 2008 12:48:31 -0700, afewtips  
<afewtips at gmail.com> wrote:

> Also,
> It is very important to maintain a development site and a production  
> site.
> Things can get very out of sync and a real big pain to fix if you are not
> careful with modifications and product installations.
> Everything should be stable in development and then moved to production.
> That is probably the best preventive medicine. Plone does have more  
> moving
> parts than what I have been exposed to in the php world.
>
>
> grahamperrin wrote:
>>
>> <http://plone.org/support>
>>
>>
>> ranworthboy wrote:
>>> I guess to really protect against something going badly wrong, the best
>>> thing is to ensure daily back-ups are done. In which case, is there a
>>> "best practise" for this?
>>
>> <http://plone.org/documentation/how-to/backup-plone>
>>
>> If you have a modern buildout-enabled installation of Plone, then some  
>> of
>> that how-to may be a little outdated. Focus primarily on the repozo
>> approach to backing up.
>>
>> Regards
>> Graham
>>
>



-- 
Alexander Limi · http://limi.net