comparison docker/README @ 9686:33303817ed37 3.2.x

Deploy webapp as d4e-river It's at the one hand expected in the print-url parameter in web.xml and at the other hand nicer than 'gwt-client-1.0-SNAPSHOT'.
author Tom Gottfried <tom@intevation.de>
date Mon, 03 Aug 2020 12:17:24 +0200
parents 537fe44f2792
children 25532d3c0af2
comparison
equal deleted inserted replaced
9685:2dad42df79a8 9686:33303817ed37
21 $ docker run --name d4eriver-artifacts --network d4e_river \ 21 $ docker run --name d4eriver-artifacts --network d4e_river \
22 -dp 8181:8181 d4e/river_artifacts 22 -dp 8181:8181 d4e/river_artifacts
23 $ docker run --name d4eriver-client --network d4e_river \ 23 $ docker run --name d4eriver-client --network d4e_river \
24 -v $PWD:/opt/d4e/river -dp 8080:8080 d4e/river_client 24 -v $PWD:/opt/d4e/river -dp 8080:8080 d4e/river_client
25 25
26 The application should now be accessible on your docker host under /d4e-river.
27 See docker/flys_user_file for credentials.
28
26 29
27 TODO: 30 TODO:
28 _ Avoid having to change configuration manually 31 _ Avoid having to change configuration manually
29 _ Allow running artifact server with `-v $PWD:/opt/d4e/river' 32 _ Allow running artifact server with `-v $PWD:/opt/d4e/river'
30 (currently this leads to missing h2 databases) 33 (currently this leads to missing h2 databases)

http://dive4elements.wald.intevation.org