Record the design decisions behind the Nuxt site as an OKF v0.2 bundle: dev
container shape, build layer order, build context filter, repository and
compose layout, and the mockup layout, plus the open questions.
Conformant per the spec: every concept carries a non-empty type, the reserved
index and log files follow their structures, and every internal link resolves.
CV_Site_Nuxt/ owns its images: Dockerfile.dev and Dockerfile live with the
application they build.
Local_Development/ is the stack entry point. Its docker-compose.yml builds
the application by relative path (../CV_Site_Nuxt) rather than duplicating any
build definition.
The design mockups live in Local_Development/design/.
This knowledge bundle lives inside the application repository it describes,
which the format allows for a bundle kept as a subdirectory of a larger
repository.
Why
A Dockerfile is part of the application, not part of the environment that runs
it. Keeping it with the app means the image definition is versioned, reviewed and
released with the code it builds, and the compose file stays a thin description
of how the pieces are wired together for local work.
Consequences
The compose file cannot be built from a checkout of Local_Development/ alone;
it needs the sibling application repository present.
Adding a service means adding a compose entry that points at another
repository's Dockerfile.
State
The compose file is being written and is not yet valid: the build key is
malformed and the port entry is empty. The shape of the mount it will use is still
an open question.