GeoIP database location should not be hardcoded (and updated)

Description

Currently, the location of the GeoIP database is defined in the web.xml file. Greater control can be had when that configuration is placed in the Tomcat context (much like does for the database).

While we're at it, it would be good to decouple the GeoIP database location from the build artifact location (builds-path).

Additionally, we might want to update the database itself (I believe it's from 2006).

Using an context-param, much like what's being done for the builds-path, should be used to configure the location for the GeoIP database. That configuration should, however, not be added to the web.xml file that's part of the webapp, but to the Tomcat context, as described in http://tomcat.apache.org/tomcat-8.0-doc/config/context.html#Context_Parameters

An updated database can be obtained here: http://dev.maxmind.com/geoip/legacy/downloadable/

Environment

None

Activity

Show:
Guus der Kinderen
May 26, 2016, 9:52 PM

The webapplication is modified to read the location from a context parameter, named geoip-database-path.

The following element was added to the Tomcat context.xml on the old Contegix host (which points to the directory where the old file was, but refers to a freshly downloaded variant. The old file still exist but should go unused):

The following element was added to the Tomcat context.xml on the new EC2 host (which uses the file location suggested by MaxMind):

Fixed

Assignee

Guus der Kinderen

Reporter

Guus der Kinderen

Labels

None

Expected Effort

None

Ignite Forum URL

None

Priority

Major