| 40 | | The application bundles, which includes a Solr instance app, the importer, the web app and configuration are deployed to directories under /lat/webapps/vlo, which also has symlinks for both the current production and current beta directories. These symlinks are used in the tomcat configuration so that this does not need any change when updating the version of the VLO. |
| 41 | | |
| 42 | | Most of the '''configuration''' takes place in the !VloConfig.xml file. Its format is read by both the importer and the web app and has options for both, so this can be shared in a single file. In addition, the web app has a set of context parameters to configure the location of !VloConfig.xml that should be used, and to ''optionally'' override the Solr base URL. |
| | 40 | The application bundles, which includes a Solr instance app, the importer, the web app and configuration are deployed to directories under /srv/webapps/vlo, with a persistent symlink to the current version. These symlinks are used in the tomcat configurations so that this does not need any change when updating the version of the VLO apart from the version specific configuration requirements (as documented in the upgrade instructions). |
| | 41 | |
| | 42 | Most of the '''configuration''' takes place in the `VloConfig.xml` file (the [https://github.com/clarin-eric/VLO/blob/master/vlo-commons/src/main/resources/VloConfig.xml template] - with Maven properties as placeholders - can be found in the sources). Its format is read by both the importer and the web app and has options for both, so this can be shared in a single file. In addition, the web app has a set of context parameters to configure the location of `VloConfig.xml` that should be used, and to ''optionally'' override the Solr base URL. The configuration typically file references (via [https://en.wikipedia.org/wiki/XLink XLink]) an external list of data roots that are environment specific. |
