[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-deployment] branch master updated: README
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-deployment] branch master updated: README |
Date: |
Thu, 05 Jan 2017 11:39:20 +0100 |
This is an automated email from the git hooks/post-receive script.
marcello pushed a commit to branch master
in repository deployment.
The following commit(s) were added to refs/heads/master by this push:
new 53fd6b5 README
53fd6b5 is described below
commit 53fd6b554e7a03bf046e20ef9c4b8f541a5f7cfc
Author: Marcello Stanisci <address@hidden>
AuthorDate: Thu Jan 5 11:39:11 2017 +0100
README
---
docker/README | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/docker/README b/docker/README
index a3e303b..2f692bc 100644
--- a/docker/README
+++ b/docker/README
@@ -1,4 +1,4 @@
-=== The Compose way ===
+=== Dockerizing the Exchange ===
This section shows how to run a "dockerized" exchange.
The exchange uses postgresql (container) and is served
@@ -8,6 +8,9 @@ The docker's tools needed are: docker, docker-compose,
docker-machine.
Please refer to Docker's official documentation for their installation
instructions.
+Before starting to build the exchange's image, make sure a docker-machine
+instance is up and running.
+
1. Build the images.
From <THIS_REPO/docker>, give:
@@ -20,14 +23,14 @@ and nginx images.
2. Launch the service.
The following command launches the exchange and all other services
-it depends on.
+it depends on. From the same directory as the previous step, issue:
$ docker-compose up
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.
+PS. Errors about existing roles/databases can be ignored.
3. Test
@@ -42,20 +45,21 @@ $ curl http://`docker-machine ip`:80/keys
=== How to use these images ===
-From a "docker ready" environment, you need to (1) build the
-image and (2) run it.
+This section explains how to (1) build and (2) run individual
+images -- that is often not useful to run services, as they need
+to be "composed" in order to work properly.
(1) is done by:
$ docker build -t taler/base <THIS_REPO>/docker/base/
$ docker build -t taler/exchange <THIS_REPO>/docker/exchange/
+Note that the value passed to option -t is completely arbitrary.
+
(2) is done by:
$ docker run -it taler/exchange
-Note that the value passed to option -t is completely arbitrary.
-
=== How to destroy them ===
Consider also the --no-cache option to force a rebuild.
--
To stop receiving notification emails like this one, please contact
address@hidden
- [GNUnet-SVN] [taler-deployment] branch master updated: README,
gnunet <=