Docker image: web app + relay for the LAN (D-036) #93
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#93
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Merged in #94. Verified:
tools/web-image-smoke.shpasses (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.