gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-deployment] 16/16: Update README


From: gnunet
Subject: [GNUnet-SVN] [taler-deployment] 16/16: Update README
Date: Thu, 05 Jan 2017 16:37:03 +0100

This is an automated email from the git hooks/post-receive script.

marcello pushed a commit to branch master
in repository deployment.

commit 6564f8da1eace6f6675bfdad1cf6259595dc7f81
Author: Marcello Stanisci <address@hidden>
AuthorDate: Thu Jan 5 16:34:33 2017 +0100

    Update README
---
 docker/README | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/docker/README b/docker/README
index ff8ee2a..b82f510 100644
--- a/docker/README
+++ b/docker/README
@@ -17,7 +17,7 @@ docker-machine instance is up and running.
 <COMPONENT> is either 'exchange' or 'merchant', depending on what is
 to be built.
 
-From <THIS_REPO/<COMPONENT>/docker>, give:
+From <THIS_REPO/docker/<COMPONENT>, give:
 
 $ docker-compose build
 
@@ -33,16 +33,18 @@ $ docker-compose up
 
 If everything worked as expected, you should see some live logging
 from all the containers.
-
-PS. Errors about existing roles/databases can be ignored.
+(Errors about existing roles/databases can be ignored.)
 
 3. Test
 
 Issue the following command to see if the <COMPONENT> has been
 correctly installed and launched.
 
-# Some 'greeting' message should be returned.
-$ curl http://`docker-machine ip`:80/
+# Some 'greeting' message should be returned.  Note, the
+# service runs on port 80.
+
+$ curl http://`docker-machine ip`/
+
 
 === How to use these images ===
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]