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


Build:

$ docker build -f docker/Dockerfile.db -t d4e/river_db .
$ docker build -f docker/Dockerfile.artifacts -t d4e/river_artifacts .
$ docker build -f docker/Dockerfile.gwt-client -t d4e/river_client .


Run:

$ docker network create d4e_river
$ docker run --name d4eriver-db  --network d4e_river \
    -dp 2345:5432 d4e/river_db:latest
$ docker run --name d4eriver-artifacts --network d4e_river \
    -dp 8181:8181 d4e/river_artifacts
$ docker run --name d4eriver-client --network d4e_river \
    -v $PWD:/opt/d4e/river -dp 8080:8080 d4e/river_client

The application should now be accessible on your docker host under /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