Document running webhooker under upaas (closes #323) #324

Merged
clawbot merged 2 commits from issue-323-running-under-upaas into next 2026-09-28 12:30:33 +02:00
2 Commits
Author SHA1 Message Date
sneak 8fa7dfae53 Reach the upaas app over a Docker network, not a port mapping
check / check (push) Successful in 7s
upaas publishes every mapped port on all host interfaces, which would
expose the plain-HTTP admin UI and receiver. The section now says to
add no port mapping, to put the app on the reverse proxy's Docker
network, and that the proxy reaches it at the upaas container name on
port 8080.

TRUSTED_PROXIES is the proxy's address on that network; the log hint
now points at a proxied request's line, since health-check lines show
::1.

Model: opus-5-5
2026-09-28 10:04:29 +00:00
clawbot c012cd6898 Document running webhooker under upaas (closes #323)
check / check (push) Successful in 6s
Adds a short "Running under upaas" section to the README, next to
"Running with Docker": the container port, the data volume and the
commands that create it, the environment variables upaas should set,
the health check upaas reads after a deploy, and where the first-run
admin password appears and how to reset it.

upaas bind-mounts a host directory it does not create, and a
directory made by root stops the container at its data directory
lock. The section has the operator create the directory owned by
UID 1000 before the first deploy; the image is unchanged.

Model: opus-5-5
2026-09-28 09:17:22 +00:00