The Dockerfile uses a multistage build to first build the artifacts
using maven. Then it copies the artifacts into a final image which
exposes the port and starts the pipeline.

If PIPELINE2_AUTH_CLIENTKEY and/or PIPELINE2_AUTH_CLIENTSECRET are
defined in the environment, when starting the pipeline, use those
values. This simplyfies dockerization of the pipeline.

that is used everywhere else, for example in the default config of the
pipeline cli

so that it can be set at run time for example when starting a Docker
image and remove it from the system.properties (otherwise setting it
as an option when starting the JVM seems to have no effect)

The test starts two containers based on the same image. One for the
pipeline itself and a second one for the cli. It then starts a script
from the cli.

This reverts 36ed956 and f23c1d6.

Also add a Makefile

and add it to the Makefile

…m properties

- PIPELINE2_HOME
- PIPELINE2_BASE
- PIPELINE2_DATA
- PIPELINE2_WS_LOCALFS
- PIPELINE2_WS_AUTHENTICATION

*nix only.

because you can now directly specify the Pipeline properties through
environment variables. Note that this will only work for system
properties that start with "org.daisy.pipeline" though.

Instead use the PIPELINE2_WS_LOCALFS and PIPELINE2_WS_AUTHENTICATION
environment variables directly.

see #137

See https://docs.docker.com/engine/reference/builder/#healthcheck