From eb71dd48a03fe6e45977e7c992b4eee4cb804bb7 Mon Sep 17 00:00:00 2001 From: SOFe Date: Fri, 11 Jan 2019 17:02:34 +0800 Subject: [PATCH] Document that NGROK_PORT supports non-local services (#32) https://ngrok.com/docs#non-local Very useful with docker-compose. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 355b0be..f1c1da6 100644 --- a/README.md +++ b/README.md @@ -46,7 +46,7 @@ Additionally, you can specify one of several environment variable (via `-e`) to * `NGROK_USERNAME` - Username to use for HTTP authentication on the tunnel. You must also specify an authentication token. * `NGROK_PASSWORD` - Password to use for HTTP authentication on the tunnel. You must also specify an authentication token. * `NGROK_PROTOCOL` - Can either be `HTTP` or `TCP`, and it defaults to `HTTP` if not specified. If set to `TCP`, Ngrok will allocate a port instead of a subdomain and proxy TCP requests directly to your application. - * `NGROK_PORT` - Port to expose (defaults to `80` for `HTTP` protocol). + * `NGROK_PORT` - Port to expose (defaults to `80` for `HTTP` protocol). If the server is non-local, the hostname can also be specified, e.g. `192.168.0.102:80`. * `NGROK_REGION` - Location of the ngrok tunnel server; can be `us` (United States, default), `eu` (Europe), `ap` (Asia/Pacific) or `au` (Australia) * `NGROK_BINDTLS` - Toggle tunneling only HTTP or HTTPS traffic. When `true`, Ngrok only opens the HTTPS endpoint. When `false`, Ngrok only opens the HTTP endpoint