eZ Community » Forums » Discussions » The completely unofficial eZ Publish...
expandshrink

Friday 04 March 2011 4:13:41 pm - 7 replies

» Read full blog post

Introduction

 

This is a checklist of actions for an update of an eZ Publish website. Comments/contributions are welcome.

Friday 04 March 2011 5:25:47 pm

Thanks, Gaetano--especially for the tip on how to "warm up" the caches!

Saturday 05 March 2011 2:41:36 am

Great checklist. Hands up who wishes that making an update were simpler? Of course, a lot can be scripted, BUT, I would request that some serious thought is put into making updating the following easier:

  1. roles & policies
  2. workflows

     

  3. sections

     

  4. object states definitions

If there was an option for packaging up content classes and any associated roles & policies, that would make life so much easier!

Monday 07 March 2011 12:26:49 pm

Interesting checklist. For "[optional] put the public website offline" part, I wrote an article almost 3 years ago with a way to do that in the Apache configuration, there's also alternatives ways of doing the same things in the comments.

Cheers

Saturday 12 March 2011 10:01:58 am

Followed this checklist yesterday, everything went smooth without any hickups. Had a backup ready just in case, but not needed. Thanks for the writeup, was helpfull.

Monday 14 March 2011 11:11:46 pm

Nice checklist... Here are two little details also worth mentioning:

  • regenerate static cache before putting the site online (bin/php/makestaticcache.php)
  • test the upgraded site on the server before putting it online happy.gif Emoticon

Friday 16 September 2011 4:16:19 am

The reply has been removed because of violation of forum rules.

Friday 24 May 2013 6:52:51 pm

A couple other elements for your consideration:

  • After deploying code, confirm that the files have the correct ownership and file permissions. These should enable Apache to do what it needs to do, while at the same time afford security. We have a script we run for this purpose.
  • To decrease production's downtime, some of the database changes, if done manually, can be done prior to taking the site offline. For example, if you need to add a new content class, and perhaps even populate it, or if you need to add a new section, these changes may be able to be done earlier in the process.
expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from