commit 70d044fc48179106c3067c59b5fee007fc0e03f6
parent 50c8842594cf3ab35f5a474ff96595df178a295a
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date: Wed, 4 Jan 2017 20:45:49 +0100
README Dockerization
Diffstat:
1 file changed, 35 insertions(+), 8 deletions(-)
diff --git a/docker/README b/docker/README
@@ -1,17 +1,44 @@
-=== The Compose way ==
+=== The Compose way ===
-This way of building things is the preferred one:
-just running,
+This section shows how to run a "dockerized" exchange.
+The exchange uses postgresql (container) and is served
+by nginx (container).
+
+The docker's tools needed are: docker, docker-compose, docker-machine.
+Please refer to Docker's official documentation for their installation
+instructions.
+
+1. Build the images.
+
+From <THIS_REPO/docker>, give:
+
+$ docker-compose build
+
+This command builds the 'base' image and pulls down the postgresql
+and nginx images.
+
+2. Launch the service.
+
+The following command launches the exchange and all other services
+it depends on.
$ docker-compose up
-from <THIS_REPO/docker>, should build all the images.
+If everything worked as expected, you should see some live logging
+from all the containers, on the console.
+
+PS. Errors about existing roles/dataabases can be ignored.
+
+3. Test
+
+Issue the following command to see if the exchange has been correctly
+installed and launched.
+
+$ curl http://`docker-machine ip`:80/
-Only the base image and the exchange are currently supposed
-to be built this way.
+and
-Ideally, a compose recipe for the exchange and one for merchant
-backend should be made available.
+$ curl http://`docker-machine ip`:80/keys
=== How to use these images ===
