You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,6 +198,7 @@ Settings in this part is immutable, you have to redeploy HAProxy service to make
198
198
199
199
|Environment Variable|Default|Description|
200
200
|:-----:|:-----:|:----------|
201
+
|ADDITIONAL_BACKENDS||list of additional backends to balance. The format is `backend name, FORCE_SSL(True|False), server name, host:port, options`|
201
202
|ADDITIONAL_SERVICES||list of additional services to balance (es: `prj1:web,prj2:sql`). Discovery will be based on `com.docker.compose.[project|service]` container labels. This environment variable only works on compose v2, and the referenced services must be on a network resolvable and accessible to this containers.|
202
203
|BALANCE|roundrobin|load balancing algorithm to use. Possible values include: `roundrobin`, `static-rr`, `source`, `leastconn`. See:[HAProxy:balance](https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4-balance)|
203
204
|CA_CERT_FILE||the path of a ca-cert file. This allows you to mount your ca-cert file directly from a volume instead of from envvar. If set, `CA_CERT` envvar will be ignored. Possible value: `/cacerts/cert0.pem`|
@@ -210,6 +211,7 @@ Settings in this part is immutable, you have to redeploy HAProxy service to make
210
211
|EXTRA_GLOBAL_SETTINGS||comma-separated string of extra settings, and each part will be appended to GLOBAL section in the configuration file. To escape comma, use `\,`. Possible value: `tune.ssl.cachesize 20000, tune.ssl.default-dh-param 2048`|
211
212
|EXTRA_ROUTE_SETTINGS||a string which is append to the each backend route after the health check, can be over written in the linked services. Possible value: "send-proxy"|
212
213
|EXTRA_SSL_CERTS||list of extra certificate names separated by comma, eg. `CERT1, CERT2, CERT3`. You also need to specify each certificate as separate env variables like so: `CERT1="<cert-body1>"`, `CERT2="<cert-body2>"`, `CERT3="<cert-body3>"`|
214
+
|FORCE_DEFAULT_BACKEND| True | set the default_service as a default backend. This is useful when you have more than one backend and you don't want your default_service as a default backend
213
215
|HEALTH_CHECK|check|set health check on each backend route, possible value: "check inter 2000 rise 2 fall 3". See:[HAProxy:check](https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#5.2-check)|
214
216
|HTTP_BASIC_AUTH||a comma-separated list of credentials(`<user>:<pass>`) for HTTP basic auth, which applies to all the backend routes. To escape comma, use `\,`. *Attention:* DO NOT rely on this for authentication in production|
215
217
|MAXCONN|4096|sets the maximum per-process number of concurrent connections.|
@@ -507,4 +509,4 @@ Legacy links:
507
509
In most cases, `dockercloud/haproxy` will configure itself automatically when the linked services change, you don't need to reload it manually. But for some reason, if you have to do so, here is how:
508
510
509
511
*`docker exec <haproxy_id> /reload.sh`, if you are on the node where dockercloud/haproxy deploys
510
-
*`docker-cloud exec <haproxy_uuid> /reload.sh`, if you use docker-cloud cli
512
+
*`docker-cloud exec <haproxy_uuid> /reload.sh`, if you use docker-cloud cli
0 commit comments