You can now configure host -> container proxy port mappings
The UI is handled by the proxy interface plugin by setting the DOKKU_PROXY_PORT_MAP config variable in the format of scheme:host-port:container-port. The default nginx-vhosts proxy plugin supports both the http and https schemes.
Default port mappings
buildpack apps will be set to http:80:5000 and will also include https:443:5000 if SSL is enabled.
dockerfile apps with explicitly exposed ports (i.e. using the EXPOSE directive) will be configured with a listener on each exposed port that proxies to the same port of the deployed application container.
You may override this behavior with the proxy:ports-* commands or by directly setting DOKKU_PROXY_PORT_MAP with the config:set command
dockerfile apps without explicitly exposed ports will behave the same as a buildpack app
NOTE: These defaults are not automatically changed on subsequent pushes and must be manipulated with the aforementioned commands
Calling the dokku binary
Plugins should not call the dokku binary directly. Clients using the --app argument are potentially broken, amongst others, when doing so. Instead, please source the functions file for a given plugin when attempting to call Dokku internal functions. As a result, the following Dokku commands are no longer publicly exposed: