Forum .LRN Q&A: Re: Guidelines on how to upgrade dotLRN

Collapse
Posted by Malte Sussdorff on
Upgrade Postgresql:

- Install 7.4.6 in paralell
- Either dump/import (works without problems) or do a direct database transfer between both running instances (it is somewhere detailed at the postgres site).

Upgrade AOLserver:

- Use latest code from CVS, especially with nsopenssl involved. Works like a charm with me, but you might want to confirm with MIT. Otherwise install pound for SSL and run AOLserver 4.09 behind it.

Upgrade .LRN:

- Which version do you come from in the first place?
- Bug Tracker upgrade works normally, if you are already at 1.2d1
- Content repository does not provide to be a problem, though I have not tested it with files stored within the database.
- Core .LRN packages have upgrade scripts, at least they have been working on a step by step basis and otherwise been fixed by Galileo, MIT or myself.
- In general: Use the APM (/acs-admin/apm) for the upgrade, not the installer.

Obviously you should run the upgrade on the copied 7.4.6 database so you still have your old data if something goes wrong :). And make at least one test run before, writing down all the steps you did in what order. And follow these steps once you do the final (live migration).