Docker image: web app + relay for the LAN (D-036) #93

Closed
opened 2026-10-18 08:50:44 +00:00 by littlefox · 1 comment
Owner

User: "Getting a public web-server for the protocol relay for the web-app is gonna take some time. To move forward faster it is better if we can package the relay as a nice container and run it here in the local network in the mean time. I am the only human interacting with this for the time being anyway. Package it for docker, with an Installation guide. Everything should be as automatic and painless as possible for deployment."

One image with the web build (Caddy) and kom-relay, published to forge's registry; compose file + install guide; config by env. Stopgap for #71.

User: "Getting a public web-server for the protocol relay for the web-app is gonna take some time. To move forward faster it is better if we can package the relay as a nice container and run it here in the local network in the mean time. I am the only human interacting with this for the time being anyway. Package it for docker, with an Installation guide. Everything should be as automatic and painless as possible for deployment." One image with the web build (Caddy) and kom-relay, published to forge's registry; compose file + install guide; config by env. Stopgap for #71.
Author
Owner

Merged in #94. Verified: tools/web-image-smoke.sh passes (browser login through the image, TLS to the devserver). The compose file runs with its defaults (one logged-out probe to kom.lysator.liu.se). The container becomes healthy, and Docker restarts it after the relay is killed. The image is published and pullable without login. CI run #171 is green.

Merged in #94. Verified: `tools/web-image-smoke.sh` passes (browser login through the image, TLS to the devserver). The compose file runs with its defaults (one logged-out probe to kom.lysator.liu.se). The container becomes healthy, and Docker restarts it after the relay is killed. The image is published and pullable without login. CI run #171 is green.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
littlefox/neokom#93
No description provided.