Skip to content
geOrchestra configuration directory for generic wars & Debian packages (eg: /etc/georchestra)
JavaScript Smarty
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
analytics
atlas
cas
console
extractorapp
geonetwork
geoserver
geowebcache
header
mapfishapp
mapstore
security-proxy
.gitignore
README.md
default.properties

README.md

geOrchestra default datadir

This repository contains the default configuration files for geOrchestra modules, and can be used as a reference to build your own "geOrchestra datadir". We call this a "datadir" for the similarity with the well-known GeoServer and GeoNetwork datadirs, but this directory is not meant to host geographic data.

At startup, geOrchestra applications running inside a servlet container having the extra georchestra.datadir parameter, will initialize themselves with the configuration contained in the directory that this parameters points to.

Debian packages already come with their own version of the datadir, but the WARs we provide don't. That is the reason why this directory is provided here.

Usage

In order to use this datadir:

  • simply clone this repository (typically in /etc/georchestra but it might be elsewhere)
  • checkout the branch matching your geOrchestra version (eventually prefixed with docker- if you use official docker images)
  • customize the different configuration files (see below)
  • launch your servlet container with an extra parameter, typically georchestra.datadir=/etc/georchestra

For instance, with tomcat, you may create a ${CATALINA_HOME}/bin/setenv.sh file with:

export CATALINA_OPTS="${CATALINA_OPTS} -Dgeorchestra.datadir="/etc/georchestra"

Note that if you are developing, and running the servlet container with the Maven embedded Jetty server, by default, the datadir will be set to /etc/georchestra/, and you only need to launch mvn jetty:run. If you need to point to another location, say /etc/anotherlocation/, you will have to pass it to Jetty: mvn -Dgeorchestra.datadir=/etc/anotherlocation jetty:run.

3-steps editing

Before using this datadir, you should at least change the default FQDN (georchestra.mydomain.org) for yours. This can be done very easily with eg:

cd /etc/georchestra
find ./ -type f -exec sed -i 's/georchestra.mydomain.org/my.fqdn/' {} \;

...where my.fqdn is your server's FQDN.

Next thing to do, for security, is changing the password of the geoserver_privileged_user, that is internally used by several geOrchestra modules:

cd /etc/georchestra
find ./ -type f -exec sed -i 's/gerlsSnFd6SmM/'$(pwgen 16 1)'/' {} \;

Remember to change it in your LDAP too !

Finally, you should head to ReCAPTCHA and get an account for your service. Once you're done, fill in the public and private keys in the console/console.properties file.

Restart your tomcat or jetty services when done with datadir editing.

Notes

There are plenty of other configuration options available, so feel free to browse the sub-folders of this repository and read the comments to make your mind.

We do recommend that you:

You can’t perform that action at this time.