docs/content/engine/security/https
David Karlsson b20c46a615 chore: unpublish README files in content dir
Adds hugo build options that prevents these READMEs from being
published.

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
2024-02-01 15:49:46 +01:00
..
Dockerfile migrate to hugo 2023-08-22 09:41:02 +02:00
Makefile migrate to hugo 2023-08-22 09:41:02 +02:00
README.md chore: unpublish README files in content dir 2024-02-01 15:49:46 +01:00
make_certs.sh migrate to hugo 2023-08-22 09:41:02 +02:00
parsedocs.sh migrate to hugo 2023-08-22 09:41:02 +02:00

README.md

_build
list publishResources render
never false never

This is an initial attempt to make it easier to test the TLS (HTTPS) examples in the protect-access.md doc.

At this point, it is a manual thing, and I've been running it in boot2docker.

My process is as following:

$ boot2docker ssh
root@boot2docker:/# git clone https://github.com/moby/moby
root@boot2docker:/# cd docker/docs/articles/https
root@boot2docker:/# 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)

root@boot2docker:/# sudo make run

Start another terminal:

$ boot2docker ssh
root@boot2docker:/# cd docker/docs/articles/https
root@boot2docker:/# make client

The last connects first with --tls and then with --tlsverify, both should succeed.