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.
* Adds option for turning off basic auth for selected services (#154)
* Allow a service to be configured as failover for another service in the same backend (#120)
* Added support for hot-failover mode
* Updated README
* Add ability to pass hashed password credentials to HAproxy. (#107)
* Remove DHE-RSA-AES128-SHA from SSL_BIND_CIPHERS (#103)
* fixed tests error by PRs
* do not return haproxy ingress network (#160)
* fix the error introduced by EXCLUDE_BASIC_AUTH
* bump version
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,8 +156,8 @@ Similar to using legacy links, here list some differences that you need to notic
156
156
Once the stack is up, you can scale the web service using `docker-compose scale web=3`. dockercloud/haproxy will automatically reload its configuration.
157
157
158
158
#### Running with Docker Compose v2 and Swarm (using envvar)
159
-
When using links like previous section, the Docker Swarm scheduler can be too restrictive.
160
-
Even with overlay network, swarm (As of 1.1.0) will attempt to schedule haproxy on the same node as the linked service due to legacy links behavior.
159
+
When using links like previous section, the Docker Swarm scheduler can be too restrictive.
160
+
Even with overlay network, swarm (As of 1.1.0) will attempt to schedule haproxy on the same node as the linked service due to legacy links behavior.
161
161
This can cause unwanted scheduling patterns or errors such as "Unable to find a node fulfilling all dependencies..."
162
162
163
163
Since Compose V2 allows discovery through the service names, Dockercloud haproxy only needs the links to indentify which service should be load balanced.
@@ -214,6 +214,7 @@ Settings in this part is immutable, you have to redeploy HAProxy service to make
214
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
215
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)|
216
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|
217
+
|HTTP_BASIC_AUTH_SECURE||a comma-separated list of credentials(`<user>:<encrypted-pass>`) for HTTP basic auth, which applies to all the backend routes. To escape comma, use `\,`. See:[HAProxy:user](https://cbonte.github.io/haproxy-dconv/1.5/configuration.html#3.4-user)*Attention:* DO NOT rely on this for authentication in production|
217
218
|MAXCONN|4096|sets the maximum per-process number of concurrent connections.|
218
219
|MODE|http|mode of load balancing for HAProxy. Possible values include: `http`, `tcp`, `health`|
219
220
|MONITOR_PORT||the port number where monitor_uri should be added to. Use together with `MONTIOR_URI`. Possible value: `80`|
@@ -238,9 +239,11 @@ Settings here can overwrite the settings in HAProxy, which are only applied to t
238
239
|BALANCE|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)|
239
240
|COOKIE|sticky session option. Possible value `SRV insert indirect nocache`. See:[HAProxy:cookie](http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4-cookie)|
240
241
|DEFAULT_SSL_CERT|similar to SSL_CERT, but stores the pem file at `/certs/cert0.pem` as the default ssl certs. If multiple `DEFAULT_SSL_CERT` are specified in linked services and HAProxy, the behavior is undefined|
241
-
|EXCLUDE_PORTS|comma separated port numbers(e.g. 3306, 3307). By default, HAProxy will add all the ports exposed by the application services to the backend routes. You can exclude the ports that you don't want to be routed, like database port|
242
+
|EXCLUDE_BASIC_AUTH|if set, the application by the application services to the backend routes. You can exclude the ports that you don't want to be routed, like database port|
243
+
|EXCLUDE_PORTS|if set(any value) and `HTTP_BASIC_AUTH` global setting is set, no basic auth will be applied to this service.|
242
244
|EXTRA_ROUTE_SETTINGS|a string which is append to the each backend route after the health check,possible value: "send-proxy"|
243
245
|EXTRA_SETTINGS|comma-separated string of extra settings, and each part will be appended to either related backend section or listen session in the configuration file. To escape comma, use `\,`. Possible value: `balance source`|
246
+
|FAILOVER|if set(any value), it configures this service to be run as HAProxy `backup` for other configured service(s) in this backend|
244
247
|FORCE_SSL|if set(any value) together with ssl termination enabled. HAProxy will redirect HTTP request to HTTPS request.
245
248
|GZIP_COMPRESSION_TYPE|enable gzip compression. The value of this envvar is a list of MIME types that will be compressed. Some possible values: `text/html text/plain text/css application/javascript`. See:[HAProxy:compression](http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4-compression)|
246
249
|HEALTH_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)|
0 commit comments