☰

Updated haproxy-letsencrypt-docker.md

Dave committed 2019-05-13 03:43:21 +0000 commit 546022c51b8a1385ba837f8f5d0af2dd4f5ccae6

				haproxy-letsencrypt-docker.md
			
          @@ -2,10 +2,10 @@

           <!-- SUBTITLE: This is 3 lines of bash when docker's not involved you know -->

           # What are we doing here?

          -Let's set up [HAProxy](https://www.haproxy.org/) with some lovely free certs from [Let's Encrypt](https://letsencrypt.org/) via [certbot](https://certbot.eff.org/) for a couple of domains, each domain served from a different container, and all in docker.

          +Let's set up HAProxywith some lovely free certs from [Let's Encrypt](https://letsencrypt.org/) via [certbot](https://certbot.eff.org/) for a couple of domains, each domain served from a different container, and all in docker.

           The rules:

          -* Everything running in [docker](https://www.docker.com), and all tied together with [docker-compose](https://docs.docker.com/compose/).

          +* Everything running in docker, and all tied together with docker-compose.

           * No k8s, no swarm, just one woman/man/other and one host/VM/other. Comfortable. Oldskool.

           * We'll use [docker user-defined networks](https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks), because that's the Right Thing To Do here.

...	...	@@ -2,10 +2,10 @@
2	2	<!-- SUBTITLE: This is 3 lines of bash when docker's not involved you know -->
3	3
4	4	# What are we doing here?
5		-Let's set up [HAProxy](https://www.haproxy.org/) with some lovely free certs from [Let's Encrypt](https://letsencrypt.org/) via [certbot](https://certbot.eff.org/) for a couple of domains, each domain served from a different container, and all in docker.
	5	+Let's set up HAProxywith some lovely free certs from [Let's Encrypt](https://letsencrypt.org/) via [certbot](https://certbot.eff.org/) for a couple of domains, each domain served from a different container, and all in docker.
6	6
7	7	The rules:
8		-* Everything running in [docker](https://www.docker.com), and all tied together with [docker-compose](https://docs.docker.com/compose/).
	8	+* Everything running in docker, and all tied together with docker-compose.
9	9	* No k8s, no swarm, just one woman/man/other and one host/VM/other. Comfortable. Oldskool.
10	10	* We'll use [docker user-defined networks](https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks), because that's the Right Thing To Do here.
11	11