Mercurial > dive4elements > river
view docker/README @ 9744:b1b48fa7bd80 3.2.x
Include both database drivers in one pom.xml
This makes it unnecessary to package for a specific database and makes
it possible to connect to both database backends from the same installation
(e.g. in a Docker container).
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Tue, 30 Aug 2022 14:33:20 +0200 |
parents | d1dcb8d28b0d |
children | 1632f64aba89 |
line wrap: on
line source
Configure: _ Change 'localhost' to the hostname of your docker host in artifacts/doc/conf/floodmap.xml and artifacts/doc/conf/rivermap.xml _ Change 'example.com' to the hostname of your docker host plus ':8082' in artifacts/doc/conf/conf.xml _ Add to gwt-client/src/main/webapp/WEB-INF/config.yaml to enable map printing: - !dnsMatch host: <your-host> port: 8081 Build and run: $ cd docker $ docker-compose up The application should now be accessible on your docker host under port 8080 and path /d4e-river (e.g. http://your-host:8080/d4e-river). See docker/flys_user_file for credentials. TODO: _ Avoid having to change configuration manually _ Allow running artifact server with `-v $PWD:/opt/d4e/river' (currently this leads to missing h2 databases) _ Let all components log to stdout to enable useful usage of `docker logs' _ Something better than setting framework and http-client to a branch explicitly in the Dockerfiles