Redirecting this to the Users list, since it is an issue which affects implementers.
On Feb 9, 2008 1:11 PM, Øystein Skadsem <[EMAIL PROTECTED]> wrote: > DHIS 2 wrote: > > #237: BitRock upgrader (of database and war file) > > > ------------------------------------+--------------------------------------- > > Reporter: knutst | Owner: Øystein > > Type: Task | Status: new > > Priority: Critical | Milestone: 2.0 > > Component: Packaging/Installation | Keywords: > > > ------------------------------------+--------------------------------------- > > For every release of DHIS 2, there should be a packaged upgrader > (BitRock > > or similar) which can handle both the replacement of the war file and > the > > necessary database updates. > > I fully support this of course, and I'll look into it. But there are > some technical issues here. Putting it bluntly, I'm not sure how > feasible this is for anything but upgrades to previous installs from the > same bitrock-installers, as there is otherwise no way of knowing how > dhis is started (mysql or postgres?, jetty or tomcat?, services or not? > etc). Agreed - the standard upgraders which we publish will be linked to the previously published installers. If people select install directories different from the default, they will have to indicate that in the upgrader. For a more advanced solution, I suppose we could do a search for the installation, or more likely consult an environment variable, as you suggest below. > So I presume you meant that once 2.0 is released and I whip up a > bunch of installers for that, that we can then focus on having upgraders > ready for 2.0.1 and onward? > Yes. BUT we are also going to need specialized upgraders for existing sites such as Kerala and Gujarat. AND we have to make it as simple as possible for local implementers to create their own installers/upgraders (i.e. with their own database and WAR files - that should probably be a separate ticket). > > Also, when running such an "upgrader", it would need to somehow know > where the current dhis2 install is. Does setting an environment variable > during installation called, say, DHIS2DIR pointing to this location, and > then reading this during upgrade and failing that asking for where it is > located a decent solution? Sounds good to me - would like to see comments from others. > Alternatives include registry entries I > guess, but I'm not a fan of mucking around in there (and it's not > portable, I want a solution that I can use for linux too...) > No registry (mon)key business, please ;-) Knut
_______________________________________________ Dhis-users mailing list [email protected] http://www.hisp.info/mailman/listinfo/dhis-users
