Template configuration, useful for those who build geOrchestra
JavaScript Groovy Java CSS HTML XSLT
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
analytics/js/app
build_support
cas-server-webapp
catalogapp/app/js
excluded
extractorapp/app/js
geonetwork-client
geonetwork-main
header/img
mapfishapp
DeployScript.groovy
README.md

README.md

Template configuration for geOrchestra

This configuration folder should be considered as a starting point in order to configure your own geOrchestra instance. Fork me !

As such, it makes the following main hypotheses:

  • a single machine, "3 tomcats"-based setup, as described by the official documentation,
  • tomcat connectors configured to bind to ports 8180 (proxy/cas), 8280 (all other webapps), 8380 (geoserver) on localhost,
  • HTTPS scheme is assumed on the front web server,
  • english language is the default one,
  • minimal (production) logging level.

This configuration folder contains:

  • a build_support directory hosting:
    • a shared.maven.filters file, which lists most of the shared maven filters you want to customize for your own setup,
    • a GenerateConfig.groovy file, which is used to customize the application specific default maven filters,
  • several directories matching the names of geOrchestra modules, whose files will override the default ones in the webapp,
  • a DeployScript.groovy file, which may optionally be used to automate the deployment of geOrchestra artifacts into tomcat.
  • an excluded directory, which can be used to store extra scripts or files that are not directly related to the geOrchestra configuration. They will not be shipped into the configuration jar.

Please refer to the main configuration instructions if you want to know more about the configuration process in geOrchestra.