badblocks/docker-easy-haproxy
1
0
Fork 0
Code Activity

Make documentation clear

Browse source
This commit is contained in:
Joao Gilberto Magalhaes 2023-02-28 00:04:51 -06:00
parent c0eb766339
commit d63aeef206
3 changed files with 14 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/docker.md
View file

@ -4,8 +4,12 @@
This method will use a docker standalone installation to discover the containers and configure the HAProxy. This method will use a docker standalone installation to discover the containers and configure the HAProxy.
The only requirement is that containers and EasyHAProxy must be in the same docker network. You cannot mix docker containers with swarm containers.
If not, EasyHAProxy will connect the container with the EasyHAProxy network.
The only request is that containers and EasyHAProxy must be in the same docker network.
If you don't add to your services the same network EasyHAProxy is connected to, EasyHAProxy will attach it network to your container.
Also, it is highly recommended you create a network external to EasyHAProxy.
e.g.: e.g.:

2
docs/kubernetes.md
View file

@ -71,7 +71,7 @@ Once the container is running, EasyHAProxy will detect automatically and start t
You don't need to expose any port in your container. You don't need to expose any port in your container.
Caveats: Notes:
- At this point, the implementation doesn't support all ingress properties or wildcard domains. - At this point, the implementation doesn't support all ingress properties or wildcard domains.
- The ingress will publish the ports 80 and 443, plus 1936 if stats are enabled. - The ingress will publish the ports 80 and 443, plus 1936 if stats are enabled.

12
docs/swarm.md
View file

@ -5,13 +5,17 @@
This method will use a docker swarm installation to discover the containers and configure the HAProxy. This method will use a docker swarm installation to discover the containers and configure the HAProxy.
The advantage of this method is that you can discover containers in other nodes from the cluster. The advantage of this method is that you can discover containers in other nodes from the cluster.
The only requirement is that containers and EasyHAProxy must be in the same docker swarm network. You cannot mix docker containers with swarm containers.
If not, EasyHAProxy will connect the service with the EasyHAProxy service network.
The only request is that containers and EasyHAProxy must be in the same docker swarm network.
If you don't add to your services the same network EasyHAProxy is connected to, EasyHAProxy will attach it network to your container.
Also, it is highly recommended you create a network external to EasyHAProxy.
e.g.: e.g.:
```bash ```bash
docker network create -d overlay easyhaproxy docker network create -d overlay --attachable easyhaproxy
``` ```
And then deploy the EasyHAProxy stack: And then deploy the EasyHAProxy stack:
@ -79,8 +83,6 @@ networks:
external: true external: true
``` ```
Note: The services to be discovered **don't need** to be in the same network as EasyHAProxy is.
Once the container is running, EasyHAProxy will detect automatically and start to redirect all traffic from `example.org:80` to your container. Once the container is running, EasyHAProxy will detect automatically and start to redirect all traffic from `example.org:80` to your container.
You don't need to expose any port in your container. You don't need to expose any port in your container.