From 4d4d1e7f82592c4996650b92b01d9f4633e8878b Mon Sep 17 00:00:00 2001 From: "Kai Qiang Wu(Kennan)" Date: Tue, 23 Feb 2016 03:42:10 +0000 Subject: [PATCH] Fix doc format issue Signed-off-by: Kai Qiang Wu(Kennan) --- docs/security/https/README.md | 29 +++++++++++++++-------------- 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/docs/security/https/README.md b/docs/security/https/README.md index 1369913ed7..ff5538911c 100644 --- a/docs/security/https/README.md +++ b/docs/security/https/README.md @@ -7,26 +7,27 @@ draft = true This is an initial attempt to make it easier to test the examples in the https.md -doc +doc. -at this point, it has to be a manual thing, and I've been running it in boot2docker +At this point, it has to be a manual thing, and I've been running it in boot2docker. -so my process is +My process is as following: + + $ boot2docker ssh + $$ git clone https://github.com/docker/docker + $$ cd docker/docs/articles/https + $$ make cert -$ boot2docker ssh -$$ git clone https://github.com/docker/docker -$$ cd docker/docs/articles/https -$$ make cert lots of things to see and manually answer, as openssl wants to be interactive + **NOTE:** make sure you enter the hostname (`boot2docker` in my case) when prompted for `Computer Name`) -$$ sudo make run -start another terminal + $$ sudo make run -$ boot2docker ssh -$$ cd docker/docs/articles/https -$$ make client +Start another terminal: -the last will connect first with `--tls` and then with `--tlsverify` + $ boot2docker ssh + $$ cd docker/docs/articles/https + $$ make client -both should succeed +The last will connect first with `--tls` and then with `--tlsverify`, both should succeed.