// BUILD CONFIGURATION
Build Caching
What's currently cached, what isn't, and how that affects build time.
Docker layer caching applies within a single build the normal way (unchanged layers early in the Dockerfile are reused), but there is currently no cross-build dependency cache (e.g. a persisted node_modules or pip cache reused between separate deploys) — each build starts from a fresh clone.
The most effective thing you control is Dockerfile layer ordering: copy dependency manifests (package.json/package-lock.json, requirements.txt, go.mod) and install dependencies *before* copying the rest of the source, so that layer only invalidates when dependencies actually change rather than on every commit.