☰

Updated haproxy-letsencrypt-docker.md

Dave committed 2019-05-13 02:27:31 +0000 commit 423457e5816cc5ce14ff2771b6a516b519afd8d5

				haproxy-letsencrypt-docker.md
			
          @@ -33,6 +33,7 @@ Let's do this thing.

           # Stage 0 - setup

           This all assumes that your soon-to-be certificated domains' A records are all pointing at the docker host (or port-forwarding router, or whatever), and you can reach the docker host on port 80 and 443 from the Interwebs.

           Your docker host should have docker, docker-compose, and openssl installed (for testing), and the docker daemon should be running.

          +You should be root, or a similarly permissioned user.

           # Stage 1 - certbot

           Since this is a greenfield setup, we can let certbot take care of the initial cert request on its own - nothing should be using ports 80 or 443 for this, so certbot can listen by itself.

...	...	@@ -33,6 +33,7 @@ Let's do this thing.
33	33	# Stage 0 - setup
34	34	This all assumes that your soon-to-be certificated domains' A records are all pointing at the docker host (or port-forwarding router, or whatever), and you can reach the docker host on port 80 and 443 from the Interwebs.
35	35	Your docker host should have docker, docker-compose, and openssl installed (for testing), and the docker daemon should be running.
	36	+You should be root, or a similarly permissioned user.
36	37
37	38	# Stage 1 - certbot
38	39	Since this is a greenfield setup, we can let certbot take care of the initial cert request on its own - nothing should be using ports 80 or 443 for this, so certbot can listen by itself.