[Hippo-cms7-user] Best practice for handling a production environment

Stephan Westen 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:

> Hello,
> 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
> documents
> 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
> it
> 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
> repository.

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:
> http://n2.nabble.com/Best-practice-for-handling-a-production-environment-tp3972711p3972711.html
> Sent from the General Discussion / Features / Bugs mailing list archive at
> Nabble.com.
> _______________________________________________
> Hippo-cms7-user mailing list and forums
> http://www.onehippo.org/cms7/support/community.html


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onehippo.org/pipermail/hippo-cms7-user/attachments/20091109/9c2f0b05/attachment.htm>

More information about the Hippo-cms7-user mailing list