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

3: Re: Guidelines on how to upgrade dotLRN (response to 1)

Posted by Nima Mazloumi on 01/06/05 02:01 PM

Malte,

thank you very much for your guidelines.

Here is what I have
- bug-tracker 1.3d
- dotlrn 2.0.3
- acs-kernel 5.0.4 (like most of the OACS packages)

Is the upgrade of AOLServer and PostgreSQL necessary? Why should I dump the database (except for backup purposes) and run it on 7.4.6? Won't the upgrade work otherwise?

So should we simply replace the packages folder with the latest from oacs-5-1 branch on a running test system and then use the APM? But what exactly should I use in APM? The only

I normally use the upgrade link on /acs-admin/install but I guess that is exactly what we shouldn't do? Why is that?

Greetings,
Nima

4: Re: Re: Guidelines on how to upgrade dotLRN (response to 3)

Posted by Malte Sussdorff on 01/06/05 02:55 PM

AOLserver and Postgres is not necessary, but recommended for performance reasons. Furthermore, dumping the database and installing it on 7.4.6 gives you the safe feeling that your old site will still work, even if the upgrade fails.

Please make a fresh checkout of *all* of oacs-5-1 (not only packages) and modify the resulting /www/*.adp to your needs. This is necessary due to changes in blank-master.adp and I think standard-master.adp as well.

Using the APM is the foolproof way. From what I heard, /acs-admin/install does not execute the upgrade APM callback procs correctly (sometimes). But maybe I'm only an old hacker that is attached to the /acs-admin/apm interface :).

Bug Tracker will not give you any trouble, neither should .LRN in my experience and definitely not OpenACS itself. Be warned though to make a check on the ACS Authentication issue which is desribed in the forums quite at length.

Anything else that might go wrong will be seen on the development server where you test the upgrade.

5: Re: Re: Re: Guidelines on how to upgrade dotLRN (response to 4)

Posted by Nima Mazloumi on 01/06/05 03:05 PM

How should I use APM?

APM page offeres the following links:
- Create a new package
- Write new specification files for all installed, locally generated packages
- Load a new package from a URL or local directory.
- Install packages

Clicking on a package I am only offered the sections:
- package information
- manage
- reload
- xml .info package specification file
- disable/unistall

I cannot see any upgrade link. So how do you upgrade packages from APM? Via "Reload this package" or "Install packages." link?

Greetings,
Nima

6: Re: Re: Re: Re: Guidelines on how to upgrade dotLRN (response to 5)

Posted by Malte Sussdorff on 01/06/05 03:36 PM

Install Packages, it figures out automatically if an upgrade is needed or a new install.

7: Re: Guidelines on how to upgrade dotLRN (response to 6)

Posted by Nima Mazloumi on 01/06/05 03:41 PM

Thank you. Why do we have several ways to install/upgrade packages in OpenACS? Wouldn't it make sense to have one working solution? I know this is not the right thread to ask but the UI of APM seems confusing to me. Maybe we can tune that up a little.