☰

Updated haproxy-letsencrypt-docker.md

Dave committed 2019-05-12 21:44:00 +0000 commit 2723496ee88efe96b811b8125633c21ac13daf0a

				haproxy-letsencrypt-docker.md
			
          @@ -81,7 +81,7 @@ volumes:

             letsencrypt_etc:

           ```

          -In the above we're requesting certs for domain1 and domain2 under example.com. Replace the email to if you're playing along at home.

          +In the above we're requesting certs for domain1 and domain2 under example.com. Replace the email too if you're playing along at home.

           certbot listens on port 8000, which docker is mapping to port 80. We don't need port 443 mapped, because this is an initial request, so Let's Encrypt should be fine with port 80.

           Also of note, we're attaching a Volume to /etc/letsencrypt - that's where the certs end up, and that's how we'll make them available to haproxy.

           The command also concatenates the cert chain and private key into a format that haproxy understands, and dumps it out into the mounted volume.

...	...	@@ -81,7 +81,7 @@ volumes:
81	81	letsencrypt_etc:
82	82	```
83	83
84		-In the above we're requesting certs for domain1 and domain2 under example.com. Replace the email to if you're playing along at home.
	84	+In the above we're requesting certs for domain1 and domain2 under example.com. Replace the email too if you're playing along at home.
85	85	certbot listens on port 8000, which docker is mapping to port 80. We don't need port 443 mapped, because this is an initial request, so Let's Encrypt should be fine with port 80.
86	86	Also of note, we're attaching a Volume to /etc/letsencrypt - that's where the certs end up, and that's how we'll make them available to haproxy.
87	87	The command also concatenates the cert chain and private key into a format that haproxy understands, and dumps it out into the mounted volume.