Keep credentials and config out of the container image #3
Loading…
Reference in a new issue
No description provided.
Delete branch "config-outside-image"
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?
Summary
Ensure credentials and config can live entirely outside the container image.
Changes
conf.jsonand.envfrom the build context, so local config/secrets are never sent to the builder or baked into any layer.${VAR}references in config string values from the environment. A missing variable now aborts startup with a clear message (environment variable X is not set (referenced as ${X})).Verification
${VAR}expansion verified end-to-end (set → expanded; unset → clear failure).conf.jsonnot present in the runtime image; binary runs.- Exclude conf.json and .env from the container build context so local config/secrets are never baked into the image - Expand ${VAR} references in config string values from the environment, failing with a clear message if a referenced variable is unset - Document container usage (mounted config, env-var injection) in README