view docker/README @ 9720:13e2d38ad314 3.2.x

Improve Docker based setup _ Make CentOS based images more resilient against package installation problems _ Upgrade database image to Debian bullseye to avoid OpenSSL bug that prevented downloading demo data and do some cleanup in passing _ Add docker-compose file for more automated setup
author Tom Gottfried <tom@intevation.de>
date Thu, 24 Feb 2022 18:49:02 +0100
parents c3afc0274bba
children 28647fff733b
line wrap: on
line source
Configure:
_ Change 'localhost' to 'd4eriver-db' in artifacts/doc/conf/backend-db.xml
  and artifacts/doc/conf/seddb-db.xml
_ Change 'localhost' to '0.0.0.0' in artifacts/doc/conf/rest-server.xml
_ Change 'localhost' to 'd4eriver-artifacts' in the server-url parameter in
  gwt-client/src/main/webapp/WEB-INF/web.xml
_ Set font path to /usr/share/fonts/gnu-free/FreeSans.ttf in
  gwt-client/src/main/webapp/WEB-INF/config.yaml


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

http://dive4elements.wald.intevation.org