From a7ec68e10734a54c3e449bf4b8a3321ee5cb358e Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Fri, 24 Jun 2016 23:38:13 -0400 Subject: [PATCH] Move around doc section a bit to clarify what is available. [ci skip] --- docs/proxy.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/proxy.md b/docs/proxy.md index c1ed7b112..7b710aced 100644 --- a/docs/proxy.md +++ b/docs/proxy.md @@ -1,9 +1,13 @@ # Proxy plugin -> New as of 0.5.0 - As of dokku 0.5.0, the proxy functionality has been decoupled from the nginx-vhosts plugin into the proxy plugin. In the future this will allow other proxy software (HAProxy for example) to be used instead of nginx. +As of dokku 0.6.0, Dokku also has the ability to map host ports to container ports. + +## Container network interface binding + +> New as of 0.5.0 + ``` proxy Show proxy settings for app proxy:disable Disable proxy for app @@ -11,8 +15,6 @@ proxy:enable Enable proxy for app proxy:set Set proxy type for app ``` -## Container network interface binding - By default, the deployed docker container running your app's web process will bind to the internal docker network interface (i.e. `docker inspect --format '{{ .NetworkSettings.IPAddress }}' $CONTAINER_ID`). This behavior can be modified per app by disabling the proxy (i.e. `dokku proxy:disable `). In this case, the container will bind to an external interface (i.e. `0.0.0.0`) and your app container will be directly accessible by other hosts on your network. > If a proxy is disabled, dokku will bind your container's port to a random port on the host for every deploy, e.g. `0.0.0.0:32771->5000/tcp`.