☰

Updated haproxy-letsencrypt-docker.md

Dave committed 2019-05-13 03:40:57 +0000 commit 1abb5c56f40ce3f1fcf3e8b0e823c380553c9bae

				haproxy-letsencrypt-docker.md
			
          @@ -295,7 +295,8 @@ What doing?

           * The container is granted privileged permissions to let the docker socket work.

           ## Go!

          -Run `docker-compose up` to bring up haproxy and the letsencrypt container. certbot will (after 10 seconds) read the current certs and decide there's nothing to do, then go to sleep for a day. haproxy should start up and tell you nice things about the letsencrypt backend being up.

          +Run `docker-compose up` to bring up haproxy and the letsencrypt container. certbot will (after 10 seconds) read the current certs and decide there's nothing to do, then go to sleep for a day.

          +haproxy should start up and tell you nice things about the letsencrypt backend being up.

           # Next?

           Add your choice of backends and containers to haproxy.cfg and docker-compose.yml, and go about your business.

...	...	@@ -295,7 +295,8 @@ What doing?
295	295	* The container is granted privileged permissions to let the docker socket work.
296	296
297	297	## Go!
298		-Run `docker-compose up` to bring up haproxy and the letsencrypt container. certbot will (after 10 seconds) read the current certs and decide there's nothing to do, then go to sleep for a day. haproxy should start up and tell you nice things about the letsencrypt backend being up.
	298	+Run `docker-compose up` to bring up haproxy and the letsencrypt container. certbot will (after 10 seconds) read the current certs and decide there's nothing to do, then go to sleep for a day.
	299	+haproxy should start up and tell you nice things about the letsencrypt backend being up.
299	300
300	301	# Next?
301	302	Add your choice of backends and containers to haproxy.cfg and docker-compose.yml, and go about your business.