Document runtime, env vars, and Compose usage in README #2
Loading…
Reference in a new issue
No description provided.
Delete branch "readme-document-image-usage-env"
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?
What changed
Expanded
README.mdfrom a short image summary into full operational documentation:docker-templates(templates/traefik_certs-dumper) and this repo is the image only.docker-templatesuses the untagged image, so Compose pulls:latest, which tracks:main.1000, read-only root filesystem, and the writable paths (tmpfs plus PEM destination).ACME_FILENAMEvalidation, waiting for certificates, polling with snapshot digest and lock, runningtraefik-certs-dumper filewith v3/domain-subdir/pem flags, runningPOST_HOOK, and writing thereadymarker.ACME_FILENAME,ACME_DIR,ACME_DEST,POST_HOOK,CERTS_DUMPER_RUNTIME_DIR,CERTS_DUMPER_POLL_SECONDSwith defaults and purpose. Notes that Mailcow settings belong to the hook indocker-templates, not the entrypoint.ready).openssh-client,jq,curl,openssl, andbind-toolsfor the mounted post-hook.Why
The previous README did not describe the entrypoint behaviour, configuration surface, or how the image is consumed by the
docker-templatesservice. These additions make the contract between the image, the hook, and the Compose template explicit, and document the runtime packages needed by the post-hook.Notes