Recently I upgraded plone.org from Plone 4.2 to Plone 4.3.
Recently at the behest of Liz Leddy, I upgraded plone.org from Plone 4.2 to Plone 4.3. It’s been a while since I had the pleasure, so I thought I’d make some notes: for myself, the AI Team and anyone else interested in the process.
The first step is always to get a local copy:
$ git clone email@example.com:plone/Products.PloneOrg.git $ cd Products.PloneOrg $ cp buildout.cfg.in buildout.cfg
buildout.cfg to extend the
[buildout] # Rename to buildout.cfg and uncomment one of the profiles below extends = # Plone only, unthemed # conf/develop.cfg # Copy data local (with plone.org account) conf/database.cfg # Production (for use on plone.org server) # conf/production.cfg # Staging (for use on plone.org server) # and Deployment (for use by Jenkins, admins and developers), # fabric can be added to any of primary configurations # conf/staging.cfg # conf/fabric.cfg # Developer Database Drop; makes developer-friendly copies # of plone.org's content. # conf/devdrop.cfg
Bootstrap and run Buildout:
$ virtualenv-2.7 . $ bin/pip install zc.buildout $ bin/buildout
Make the appropriate configuration changes i.e. change
extends from 4.2 to 4.3:
[buildout] develop = . extends = http://dist.plone.org/release/4.3.1/versions.cfg versions.cfg sources.cfg extensions = # buildout.dumppickedversions buildout.threatlevel mr.developer versions = versions sources-dir = sources eggs = Pillow Products.PloneOrg Products.PloneHotfix20130618 # get us a user and group variable [env] recipe = gocept.recipe.env [grp] recipe = collective.recipe.grp
Run the upgrade locally. With plone.org data this takes about 45 minutes to an hour .
We know from upgrading locally that the process will take about 45 minutes to an hour, so you should allocate about 2 hours to do the upgrade.
main_templateto accomplish this, but ideally we’d have some functionality in Plone that allowed site administrators to easily configure status messages.
Run the upgrade. I forgot to mention earlier something very important: On plone.org, you can’t access Zope from the internet. And you can’t run the upgrade without accessing Zope. Hence run the following command to access the server, then access Plone via
$ ssh -L 8080:10.57.0.107:5011 direct.plone.org
After the upgrade finishes, click around to make sure you didn’t break anything. In my case, I broke something — I normally move
That’s it! I hope this helps folks wrap their head around the plone.org upgrade process. A few closing thoughts:
portal_skins/customto encourage folks to “please keep this area clean” — does not work.
|||It shouldn’t take this long. See: https://github.com/plone/Products.PloneOrg/commit/b04105f7c9cacf3880c12effba5ffe261d4b5163#commitcomment-3384259 for a discussion about this issue.|