Personal tools
You are here: Home Lists ZPUG DC List Archives 2005 2005-08 how to migrate/upgrade a custom product across multiple sites? / Christoph Berendes <berendes@netalyst.com>
Navigation
Log in


Forgot your password?
New user?
Mailing Lists
You can read our ZPUGDC mailing list archives online.
You can subscribe to our mailing list:
Book Review

The Definitive Guide to Plone

Reviewer: joel
 

how to migrate/upgrade a custom product across multiple sites? / Christoph Berendes <berendes@netalyst.com>

how to migrate/upgrade a custom product across multiple sites?
Christoph Berendes <berendes(at)netalyst.com>
2005-08-22 18:02:29 [ FULL ]
I've got a custom Product running in multiple plone sites (separate 
mount points), with a single Products directory.

We're continuing to develop the product. Most of the changes can be 
pushed out easily to the existing sites

However, code changes Install.py (such as new Actions) only show up when 
a new site is set up - via the Customization Policy.

I've been poking around in portal_migrations and for instance in the 
Archetypes migration script to find a model for handling existing sites 
and of course modularizing everything nicely so that the code that 
install new Tab "Foo" exists once, and is referenced both by Install.py 
and some migration script.

These migrations of ours are pretty simple, mostly action changes, but I 
want to build on the right framework.

Where could I look for good examples and documentation?

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites? / Scott Burns <scott@lentigo.net>

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites?
Scott Burns <scott(at)lentigo.net>
2005-08-22 19:37:03 [ FULL ]
Uninstalling and reinstalling via the QuickInstaller on the Plone  
control panel should take care of updating the product.  The MySite  
tutorial at:

  http://www.neuroinf.de/LabTools/MySite

has an annotated Install.py that shows how to update site property  
sheets when products are reinstalled.  The method for updating  
actions should be similar, you'd just make different API calls. ...s.

On Aug 22, 2005, at 7:06 PM, Christoph Berendes wrote:
[...]

--
Scott Burns <scott(at)lentigo.net> <http://www.lentigo.net/scott>
pub  1024D/9DA64618 2001-11-17 Scott Burns <scott(at)lentigo.net>
Fingerprint: 2F1B A22E 33C3 FD3D BBE4 D5E2 728B 4753 9DA6 4618

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites? / Alex Clark <aclark@aclark.net>

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites?
Alex Clark <aclark(at)aclark.net>
2005-08-23 12:56:55 [ FULL ]
I'm not sure I understand the question, are you looking for a way to avoid
going to each site and running the portal_quickinstaller -> reinstall
product ?

Maybe you are looking for something like this ?

http://plone.org/products/entransit/releases

On Mon, Aug 22, 2005 at 07:06:53PM -0400, Christoph Berendes wrote:[...]
[...]

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites? / Christoph Berendes <berendes@netalyst.com>

Re: [ZPUGDC] how to migrate/upgrade a custom product across multiple sites?
Christoph Berendes <berendes(at)netalyst.com>
2005-08-24 10:44:56 [ FULL ]
Alex, Scott - Thanks.

I'm looking for a couple of things:
   
    - Best practices for how Install scripts (and related stuff, e.g. 
the version file) are created/structured to make migration of sites with 
previously installed product versions easy

    - How to automate the migration of the product across multiple sites 
(all in the same Zope instance) (so the answer to Alex's first question 
is "yes" - I don't want to run quickinstalled manually)

I think the answer to Alex's second question is "no" - there is a single 
CPU running multiple sites, and the sites are dynamic, not static.

Mysite looks like a useful model.

On 8/23/05 2:00 PM, Alex Clark wrote:
[...][...][...]
Attachments: 
text.html text/html - 2953 Bytes

Powered by Plone, the Open Source Content Management System

This site conforms to the following standards: