[Hippo-cms7-user] Best practice for handling a production environment
s.westen at 1hippo.com
Mon Nov 9 15:54:34 CET 2009
On Mon, Nov 9, 2009 at 1:41 PM, Wim Ederveen <wim.ederveen at atosorigin.com>wrote:
> I was wondering if there is a best practice concerning production
> environments and the content that is created there.
> How do I update the production environment without doing a complete export
> of the content, which is not even possible, because the amounts of
> are allready choking the export right now.
I assume you mean updating the cms.war? Or do you mean something else?
> (this should be fixed in the 2.09.03 release i've heard, anyone know when
> will be released?)
we plan to tag 2.09.03 tomorrow.
> What I intend to do is update the cms.war and site.war and restart the
> enviroment without deleting my repository currently in mysql. This will
> prevent it from doing a initialisation and just use the existing
for minor version upgrade (2.09.x) updating the cms.war is fine.
> Thus I need to import changes in the hst:configuration, hst:namespaces, and
> the cnd files.
I do not get this part. Can you explain?
> Is this all or am I forgetting something.
> Or better yet, does anyone have a better idea how to tackle this problem
> Gr Wim
> View this message in context:
> Sent from the General Discussion / Features / Bugs mailing list archive at
> Hippo-cms7-user mailing list and forums
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Hippo-cms7-user