Sistema Informativo Territoriale della città di Bolzano

Quick Start

Clone the repository with the --recursive option to automatically clone submodules:

git clone --recursive https://github.com/geosolutions-it/MapStore2-C028.git

Install NodeJS >= 4.6.1 , if needed, from here.

Update npm to 3.x, using:

npm install -g npm@3

Start the demo locally:

npm cache clean (this is useful to prevent errors on Windows during install)

npm install

npm start

The demo runs at http://localhost:8081 afterwards.

Read more on the wiki.

To Create a deployable war

Edit the LDAP properties file (DO NOT COMMIT CREDENTIALS) web/ldap.properties.

You can find LDAP credentials here

During the build process the credentials will be applied to geostore-spring-security.xml, so after a deploy is only necessary to check that spring-security file is properly configured

• Only locally edit the url, userDn and password in web/ldap.properties
• Run build.sh

Test Environment

Database configuration is configured in setenv.sh. Note: Test environment is mapped as externally as mapstore3, but deployed in tomcat as mapstore2. This causes an issue because the print plugin doesn't calculate the correct path to provide in info.json (that describes the print services). For this reason MapStore2 we needed to customize PRINT_BASE_URL in setenv.sh

/var/lib/tomcat/mapstore2/bin/setenv.sh:

export JAVA_OPTS="$JAVA_OPTS -Dgeostore-ovr=file:///var/lib/tomcat/mapstore2/conf/geostore-datasource-ovr.properties"
export JAVA_OPTS="$JAVA_OPTS -DPRINT_BASE_URL=\"/mapstore3/pdf\""

Release

MapStore update procedure:

1. Update the project by updating the submodule to a specific stable branch, and apply the needed changes (see migration guide of MapStore).
2. After a deploy has been tested create a new tag version.

Tag name

For test (master) the convention for the tag names is: v[major].[minor].[patch]-rc example: v1.1.5-rc

For production the convention for the tag names is: v[major].[minor].[patch] example: v1.1.5

Note: The major here represent a very big change to the application. For normal updates (e.g. New MapStore version) increase the minor version number, for a fix, increase the patch number.

To create a tag for test, use these steps:

git checkout master
git tag v1.1.5-rc
git push origin v1.1.5-rc

For Production use these steps:

git checkout production
git tag v1.1.5
git push origin v1.1.5