dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi there.
Dear Devs,

I have made some further modifications to the installer that I would
like to bring your attention to.

The installer now copies all necessary files (birt.war, dhis.war,
dhis2-live.exe, dhis2-live.jar) at the pre-build stage from the
corresponding directories that are specified through environment
variables. The only thing that it does not do, is populate the demo
db. You will need to do that yourself by placing the H2 database in
the dhis2-live-installer\resources\demodb directory. I did it this way
so that different implementers can easily put their own DB there. In
order to get the installer to build, you will need to download the
demo db from dhis2.org and unzip it (all at one level) in the demodb
folder. I am not exactly sure why the db has been zipped up the way it
has, but I unzipped everything in the demodb folder, and it works. The
installation of the demodb is optional during the install. BIRT
installation is also optional. Depending on your implementation, you
may choose to modify the installer slightly, like removing BIRT for
example.

The only thing you need to do is execute mvn exec:exec, and the
installer will gather everything from the correct directories, and
build the installer. It will show up in the installerbuilder/output
directory.

I have tested this on XP and it works fine. Other platforms are as yet
untested.

The latest version is here.

bzr branch lp:~jason-p-pickering/+junk/dhis2-live-installer.

Be sure to review the readme file, and modify the build.sh script to
suit your needs. Feel free to contact me with more info if you have
problems.

Best regards,
Jason




On Thu, Feb 18, 2010 at 1:29 PM, Jason Pickering
<jason.p.pickering@xxxxxxxxx> wrote:
> Hi there. It is definitely possible, and Knut has already done this in
> an old installer that installed Tomcat as well. I just wanted to get
> "some" installer working, for demonstration purposes here in Zambia.
>
>  I think we should really develop a list of requirements, and go from
> there. Likely, we may have multiple installer variants. I see a few
> possibilities.
>
> 1) A vanilla H2 installer which alternatively, can be packaged with
> the Demo DB. This should be very simple based on the current BitRock
> installer.If one were to create the installer with the demo DB as part
> of the package, this is already done. Alternatively, we could allow
> the user to download it, and install it, but this is not feasible in
> this part of the world.
>
> 2) A vanilla Postgres installer, that come prepackaged with the
> Postgres binary. We already have this to some degree with the IZPack
> installer, and it should be pretty simple to do this in BitRock as
> well. It just needs some more time to figure out how to install
> postgres silently (which is already documented on the page you sent)
> and install the DB.
>
> 3) Utilizing Knut's work, a combined Postgres/Tomcat installer. I
> would really regard this as lower priority, as I see no compelling
> reason not to use the live package instead of a full-blown Tomcat
> installation for desktop installs (which was my target audience).
> There are already pretty good instructions of how to get DHIS2
> installed (either with the Debian packager) or from individual
> packages. I would think that people capable of installing Tomcat,
> should be capable of installing Postgres.
>
> The great thing about BitRock is the auto-update feature. I have not
> looked at this, but it seems to be pretty striaghtforward.
>
> Let me know what you think.
>
> Regards,
> jason
>
>
> 2010/2/18 Bob Jolliffe <bobjolliffe@xxxxxxxxx>:
>> I havent downloaded bitrock yet, but looking at the website docs, you
>> can define postinstall actions to run scripts.  So isn't it possible
>> to simply run pg_restore from here?
>>
>> 2010/2/18 Lars Helge Øverland <larshelge@xxxxxxxxx>:
>>>
>>>
>>> 2010/2/18 Jason Pickering <jason.p.pickering@xxxxxxxxx>
>>>>
>>>> Hi Lars,
>>>> Right now, there are two versions. The IZPack installer uses the
>>>> native windows MSI. The user has to install this by themselves.
>>>> The MSI handles the creation of the Postgres user, and the
>>>> installation of the service. This should really be done as a silent
>>>> install, but I did not figure out how to do this quite yet.
>>>>
>>>> I started as well on the BitRock variant, which is also in that
>>>> branch. It will install the H2 DB by default. Knut has provided a lot
>>>> of examples of BitRock installers using Postgres, but I have not
>>>> looked at them yet.
>>>>
>>>> Ideally, we should just have a single installer, and BitRock
>>>> (especially since we got the license from them) seems to be great. I
>>>> have not really figured out yet though how to get it to install
>>>> Postgres, but I am sure it is possible.
>>>>
>>>> Basically, we need create a BitRock installer that installs postgres.
>>>> A batch file could then be used to load a sample DB. Knut has already
>>>> done this in some of the older installers he created, so it should be
>>>> pretty simple. I suppose this could also be done with IZpack, in a
>>>> similar manner. The problem is that we need to be able to control the
>>>> postgres user name and password, in order to populate the DB with the
>>>> sample database.
>>>>
>>>> As for the BitRock installer, we can simple package the sample DB
>>>> along with the installer, and ask the user if they want to install it
>>>> or not. If they do, it will get copied to the /database folder,
>>>> otherwise, we will leave it empty.
>>>>
>>>> Regards,
>>>> jason
>>>>
>>>>
>>>
>>> Tutorial for silent install of postgres windows installer:
>>> http://pginstaller.projects.postgresql.org/silent.html
>>> I am not sure if this is possible but could we do this similar to how we
>>> "install" H2? Set it up, include a database, compress it and when
>>> installing, simply decompress it?
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>