58 | | Ideally, the application is run and managed via the [https://gitlab.com/CLARIN-ERIC/compose_vlo VLO docker compose configuration]. It ties together two images: [https://gitlab.com/CLARIN-ERIC/docker-vlo-beta CLARIN-ERIC/docker-vlo] and [https://gitlab.com/CLARIN-ERIC/docker-solr CLARIN-ERIC/docker-solr]. The former provides both the web app and the importer, and connects to the latter for reading and writing from/to the index. In order to make the Solr container work in this setup, it needs to be provisioned with the right configuration. In the docker compose configuration, this is done by attaching a volume to the Solr container that is initialised with the right Solr home content by a short-lived instance of the VLO image. Once could also use a host mount for this purpose. For details, see the documentation of the VLO docker compose projects and the two docker image projects. |
| 58 | Ideally, the application is run and managed via the [https://gitlab.com/CLARIN-ERIC/compose_vlo VLO docker compose configuration]. It ties together two images: [https://gitlab.com/CLARIN-ERIC/docker-vlo-beta CLARIN-ERIC/docker-vlo] and [https://gitlab.com/CLARIN-ERIC/docker-solr CLARIN-ERIC/docker-solr]. The former provides both the web app and the importer, and connects to the latter for reading and writing from/to the index. In order to make the Solr container work in this setup, it needs to be provisioned with the right configuration. In the docker compose configuration, this is done by attaching a volume to the Solr container that is initialised with the right Solr home content by a short-lived instance of the VLO image. One could also use a host mount for this purpose. Furthermore the project introduces an optional nginx proxy that provides access to the web app, various static content and takes care of compression and caching. For details, see the documentation of the VLO docker compose projects and the two docker image projects. |