From: Markus Fischer <info@fl...> - 2010-04-08 06:21:06
I'd like to test the recent added changes of Vufind on a non-productive
local server first.
I have already an older RC2 installation on this local machine. Can I
upgrade somehow or do I have do make a clean install?
If it is necessary to reinstall from scratch: may I simply
rm -r /usr/local/vufind and the start installing again?
I haven't really started looking at how upgrading will work yet, though obviously we'll write up an official upgrade procedure when version 1.0 comes along. Off the top of my head, I don't think it should be TOO complicated, but it's possible I'm forgetting something that will become obvious when actually attempting the upgrade.
There have been no database changes since RC2, so you can use the existing database from your RC2 installation without regenerating it. I don't believe there are any new PEAR dependencies since RC2, so you shouldn't have to run the install script to get those set up. There have been some changes to the Solr index schema, so you will have to reindex all of your records in the new installation. Some of the templates have also been rearranged because of the record driver code, so if you customized templates, some of that work may need to be modified with the new version. A lot of new config.ini settings have been added, but I have tried to make VuFind provide appropriate default behavior when settings are missing, so you may not have to worry about this.
Here's a recommended procedure off the top of my head -- if you try this and it doesn't work, please let me know and I should be able to help figure out what's breaking:
1.) Move your current RC2 installation somewhere so you have a backup.
2.) Install the latest trunk code in the directory that used to contain RC2. Don't bother running the install script -- just put the code in place.
3.) Copy web/conf/config.ini from your RC2 install into the new trunk install. If you customized anything else (MARC import rules, Solr schema, Jetty port, etc.) you may want to diff the new and old files and reconcile them.
4.) Reindex your records.
5.) Merge template changes, if necessary.
I think that should about cover it. Note also that tracking your VuFind changes in a local Subversion repository and using a vendor branching strategy to merge in new trunk changes is a good way to help automate some of this process in the future. There are some notes on this in the wiki on this (http://vufind.org/wiki/subversion#vendor_branching), and I'll be happy to elaborate if you are interested in learning more.
> -----Original Message-----
> From: Markus Fischer [mailto:info@...]
> Sent: Thursday, April 08, 2010 2:21 AM
> To: vufind-general@...
> Subject: [VuFind-General] Upgrading RC2 to RC2
> I'd like to test the recent added changes of Vufind on a non-productive
> local server first.
> I have already an older RC2 installation on this local machine. Can I
> upgrade somehow or do I have do make a clean install?
> If it is necessary to reinstall from scratch: may I simply
> rm -r /usr/local/vufind and the start installing again?
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> VuFind-General mailing list