Re: [Zope] How to upgrade from 2.0 to 2.1 Zope
On 12/2/99 8:26 PM, CURTIS David at David.Curtis@state.or.us wrote:
I wish to upgrade Zope, but what is the best way to do this? What is the procedure to upgrade the installation without losing data? I have several database with adapters--I would hate to have to re-do work. Thanks in advance!!!
It's simple... copy over your Data.fs file, as well as any products that you've installed. That's all there is too it. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
Christopher Petrilli <petrilli@digicool.com> wrote:
I wish to upgrade Zope, but what is the best way to do this? What is the procedure to upgrade the installation without losing data? I have several database with adapters--I would hate to have to re-do work. Thanks in advance!!!
It's simple... copy over your Data.fs file, as well as any products that you've installed. That's all there is too it.
is this really how you are doing it at DC HQ?! i was already thinking about a clean update solution with Data.fs and all products being somewhere else separated from the source code so that you can just install a new version without having to move around your old Data.fs and your products. has anybody else thought about separating code and data? thilo -- mezger@innominate.de innominate AG networking people fon: +49.30.308806-11 fax: -77 web: http://innominate.de pgp: /pgp/tm
On 3 Dec 1999, Thilo Mezger wrote:
It's simple... copy over your Data.fs file, as well as any products that you've installed. That's all there is too it.
is this really how you are doing it at DC HQ?! i was already thinking about a clean update solution with Data.fs and all products being somewhere else separated from the source code so that you can just install a new version without having to move around your old Data.fs and your products.
has anybody else thought about separating code and data?
Yes. I thought about it upgrading from 2.0 to 2.01, from 2.01 to 2.1b1, from 2.1b1 to 2.1b2, from 2.1b2 to 2.1b3 and just now to 2.1. IMHO there should definitly be a seperation of the Zope distribution and site specific stuff (including /var). Especially useful for people who need to upgrade a number of Zope servers simultaneously. Of course, this requires weeding out all the places where people have been encouranged to leave their own little messes: Products lib/python/Products External import Any others? These are just the ones I know of... -- ___ // Zen (alias Stuart Bishop) Work: zen@cs.rmit.edu.au // E N Senior Systems Alchemist Play: zen@shangri-la.dropbear.id.au //__ Computer Science, RMIT WWW: http://www.cs.rmit.edu.au/~zen
)This sounds like it is more suited for Zope-Dev at this point, thus the change) Stuart 'Zen' Bishop wrote: ...
IMHO there should definitly be a seperation of the Zope distribution and site specific stuff (including /var). Especially useful for people who need to upgrade a number of Zope servers simultaneously.
Of course, this requires weeding out all the places where people have been encouranged to leave their own little messes: Products lib/python/Products External import
Any others? These are just the ones I know of...
Hmmm .. what if: One could have a central code repository, with the above directories being configurable. That is to say, what if the start script/Xope.cgi, could get the location of these directories at runtime, like an environment variable? This would allow (AFAIK) the central source, and individual (ie, per server) products. Certainly cuts down on disk usage :-) Comments? -- In flying I have learned that carelessness and overconfidence are usually far more dangerous than deliberately accepted risks. -- Wilbur Wright in a letter to his father, September 1900
participants (4)
-
Bill Anderson -
Christopher Petrilli -
news-list.zopeļ¼ innominate.de -
Stuart 'Zen' Bishop