From 3c55ba1ea97f5d9d593ccc8a7d87a26aa2ce3268 Mon Sep 17 00:00:00 2001 From: Girish Ramakrishnan Date: Mon, 9 Jan 2017 09:01:13 -0800 Subject: [PATCH] doc: clarify httpPort --- docs/references/manifest.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/references/manifest.md b/docs/references/manifest.md index 386699c50..55664eab9 100644 --- a/docs/references/manifest.md +++ b/docs/references/manifest.md @@ -186,9 +186,10 @@ Type: positive integer Required: yes -The `httpPort` field contains the TCP port on which your app is listening for HTTP requests. This port -is exposed to the world via subdomain/location that the user chooses at installation time. While not -required, it is good practice to mark this port as `EXPOSE` in the Dockerfile. +The `httpPort` field contains the TCP port on which your app is listening for HTTP requests. This +is the HTTP port the Cloudron will use to access your app internally. + +While not required, it is good practice to mark this port as `EXPOSE` in the Dockerfile. Cloudron Apps are containerized and thus two applications can listen on the same port. In reality, they are in different network namespaces and do not conflict with each other.