Live GIS Build

About

GISVM is an Xubuntu based Virtual Machine which has been installed with a suite of the best Open Source Geospatial software. It is also used to build Arramagong, the Linux based Live DVD.

How to add your project or data to GISVM / Arramagong

All that's required to add your favorite package into GISVM is to:

• Optional: Subscribe to the Live Demo email list to discuss issues.

• Optional: Install the latest Arramamgong / GIS virtual machine to download into. (Alternatively, you may be able to get away with just using an Xubuntu or Ubuntu installation you may already have.)
  • Download the latest Arramagong / GISVM virtual machine from: http://download.osgeo.org/livedvd
  • On 1 Sept 2009, this is Arramagong_GISVM_FOSS4G2009_alpha, which is 2.3 Gig, compressed with 7 Zip, and needs to be downloaded in 4 parts, then added back together using 7 Zip.

On linux: assuming all 4 files are stored in the same folder, use a console to go to that folder and type:

7z x Arramagong_GISVM_FOSS4G2009_alpha1.7z.001

This will extract all four files automaticaly. You get 2 files named gisvm20090828x.vmdk and gisvm20090828x.vmx

• • Install into a Virtual Machine. We recommend using VMWare, but VirtualBox works also. (TBD, Explain how).

• write a shell script which installs and configures your stable package into the current GISVM virtual machine (which will usually be the same as installing on Xubuntu or Ubuntu).

• add the script to subversion, in https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

If you do not have write permission there feel free to send the script to the OSGeo live-demo mailing list as an attachment and we'll see that it makes it in.

• • TBD: Explain how to get subversion access.

• Notify the GISVM team to test your script, and will ensure to reference your script from main.sh.

Example scripts

You can see example scripts at: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:

install_mapserver.sh, which just "apt-get install mapserver"

Projects that haven't been packaged yet are slightly more complicated:

The Udig package is a good example: install_udig.sh

Build Drivers

Which version?

The criteria used to select applications for GISVM is as follows:

1. Priority goes to Ubuntu packaged software first, then Debian packaged software! This facilitates easy and reliable maintenance and update. Users will benefit from it. Programmers are encouraged to move their software into DebianGIS or UbuntuGIS repositories.
2. Stable, always! GISVM users are mainly starters. So they obviously are better with stable software. They have enough problems already and will gladly be happier without software bugs.

For people who want the latest version, they can create an alternative upgrade script.

Low Memory

Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.

1. Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
2. Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
3. Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

Directory Structure

1. Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
2. application are usually installed into /usr/lib
3. things that get executed by the user such as startup scripts or links to them should go into /usr/bin
4. startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
5. sample data and documentation goes into /usr/local/share
6. config files are stored in /etc
7. user specific config files or working directories can go into /home/user/. However, it will be appreciated if you can keep the amount of things in the user's home folder as small as possible. Symlinks into /usr/local can be useful here.