Automate port forwarding #14

Open
opened 2023-11-10 22:27:35 +00:00 by emil · 0 comments
Owner

Context

When the reverse proxy running on the Internet Gatwey forwards HTTP requests to the wiki.js server instance running in the Edge container, the request cannot reach the server instance unless LXD would be used to forward a host port to the container.

Thus, the request transparently passes through the host and gets processed by the server instance in the container.

Acceptance criteria

  1. On the server on The Edge curl https://localhost:3443 has been receiving HTTP status 200 and content related to wiki.js.
  2. On the server on The Edge curl https://localhost:3012 has been receiving HTTP status 200 and content related to the sitemap of the wiki.js instance.
  3. Only relevant when installing wiki.js.
# Context When the reverse proxy running on the Internet Gatwey forwards HTTP requests to the wiki.js server instance running in the Edge container, the request cannot reach the server instance unless LXD would be used to forward a host port to the container. Thus, the request transparently passes through the host and gets processed by the server instance in the container. # Acceptance criteria 1. On the server on *The Edge* `curl https://localhost:3443` has been receiving HTTP status `200` and content related to wiki.js. 2. On the server on *The Edge* `curl https://localhost:3012` has been receiving HTTP status `200` and content related to the sitemap of the wiki.js instance. 3. Only relevant when installing wiki.js.
emil added this to the wiki.js - installation & update project 2023-11-10 22:27:35 +00:00
emil added a new dependency 2023-11-10 22:28:03 +00:00
emil added a new dependency 2023-11-10 22:29:04 +00:00
emil added the
Edge Server
label 2023-11-10 22:38:04 +00:00
emil added a new dependency 2023-11-10 23:00:05 +00:00
emil changed title from Port forwarding on the server on The Edge to Automate port forwarding 2023-11-10 23:46:14 +00:00
Sign in to join this conversation.
No description provided.