Re: Plone - wgo

Carsten Senger <[email protected]>
Newsgroups gmane.comp.gnome.web,gmane.comp.gnome.infrastructure
Message-ID <CBA3D67D07193FAE27B105C6@kolja>
Hi Paul,

--On Sonntag, Juni 06, 2010 19:37:03 -0500 Paul Cutler <[email protected]>
wrote:

> As a follow-up to the editors instance of Plone that you installed a few
> months ago, the web team needs your help understanding how it was
> installed and how to update the version of Plone.
>
> Is this something only a GNOME sysadmin can do?

Yes, someone needes to login to the console there. AFAIKR I wrote
documentation how to deploy plone, and some some extra notes how to
deploy the editors instance as readme files:
<http://svn.plone.org/svn/collective/gnomeweb-plone/buildout/trunk/README.deployment>

Somebody started the plone instances when they went down some weeks ago, so
he will be able to update them as well.
The editors instance deployed now is probably deployed from an svn branch
(<http://svn.plone.org/svn/collective/gnomeweb-plone/buildout/branches/deploy-editors>).
`svn info` will tell you. So to update the editors instance, the admin has
to switch to trunk and rerun `bin/buildout -c deploy-editors.cfg`. This 
will update
all packages.

* Somebody has to make sure first that the editors buildout configuration
  `deploy-editors.cfg` still works and is up-to-date. The current 
configuration
  pins several packages to svn revisions.
* Before the upgrade, the admin should make a full backup of the directory
  the editors instance is deployed to.
* After the deployment is updated, the admin needs to run the plone
migration
  process.

I can take a look at the buildout tomorrow and assist an admin during the
update.

..Carsten
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.