You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
deploy/: check the downloaded binary, normalise CAMEX_POOL, a test, web_listen #205
Follow-ups for deploy/ (b90753c, the camex server in Docker), found when checking it for #202. Not blocking 5.0.0; the base image (alpine:3.20 → 3.22) and the secrets in the container's log are fixed in #202 already.
The binary is not checked.deploy/Dockerfile downloads camex-<arch>[-full] from the latest release with wget over HTTPS and runs it, with no checksum. GitHub gives the SHA256 of each release file (digest in the release's assets, gh release view latest --json assets); the Dockerfile could take it (or a CAMEX_SHA256 build argument) and check the download, as ci/build-musl.sh does for its toolchains.
CAMEX_POOL must be a network address.entrypoint.sh puts the server at the pool's address + 1, so CAMEX_POOL=10.60.1.7/22 gives 10.60.1.8/22 instead of 10.60.0.1/22. install.sh --pool takes the network of any address in it; the entrypoint should do the same, or refuse such a value.
No test. Nothing in CI builds deploy/ or starts it. A small e2e test: build the image (with CAMEX_RELEASE pointing at the binary just built), start it in a bridge network, check the files it makes (mode 0600), that the log has no network name or psk, and that a client joins with what the log says.
Activity
deploy/: Alpine 3.22, no network name or psk in the container's log