Bind‑mounted nginx.conf vs baked custom image: trade‑off for repeatable dev environments
Goal: establish a repeatable nginx developer environment that lets engineers modify configuration quickly while guaranteeing that the same binary and settings are used across all workstations. Constraints: using the official nginx image with a bind‑mounted nginx.conf provides instant visibility of edits without rebuilding the container, but it relies on host