Files
CV_Site_Nuxt/OKF_Nuxt/open-questions.md
T
Noel Sabia bb0ab03a97
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 35s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 5s
PR Check / Dependency audit (pull_request) Failing after 8s
PR Check / Dockerfile lint (droast) (pull_request) Failing after 5s
PR Check / AI code review (opencode) (pull_request) Canceled after 16s
docs: add OKF_Nuxt decision records and log
2026-10-18 18:09:45 +02:00

39 lines
2.1 KiB
Markdown

---
type: Open Questions
title: Open questions
description: Decisions still to make for the Nuxt site, with what needs each answer.
tags: [decision, open]
status: draft
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-10-18T12:41:52Z }
---
| Question | Needed by | Default if nobody decides |
|---|---|---|
| Shape of the production image: a runnable Node server, or static `.output/public/` files for the gateway to embed | the next Dockerfile step | None. The empty `Dockerfile` stays empty. |
| How the compose service mounts the source: the whole repository plus a volume for `node_modules`, or only the directories that get edited | finishing `Local_Development/docker-compose.yml` | None. The compose file is not yet valid. |
| Which pnpm version the production image pins | writing the production image | The same as dev, 11.26.0. |
| Whether these decisions stay in this bundle or fold into the sibling `OKF_CV_Website` bundle, which already describes the frontend at design level | after the production image exists | None. |
# The mount trade-off, in detail
Measured on the whole-repository mount:
* An anonymous volume is created once. After a dependency change the stale
contents persist unless the volume is renewed, and the renewal command has not
been tested.
* Docker creates an empty, root-owned `node_modules` directory in the repository
on the first run, unless that directory already exists.
The alternative — mounting only the directories that get edited — removes the
volume, the renewal step and the root-owned directory entirely, and keeps `.nuxt`
inside the container rather than in the working tree. It costs one compose line
per top-level directory, so a new directory silently fails to appear in the
container until the compose file is updated.
# Related
The Nuxt frontend is described at design level in `OKF_CV_Website`, in
`architecture/frontend.md` and `decisions/static-nuxt-in-gateway.md`. Those
documents state that the site is generated to static files and embedded in the
gateway image, which is an input to the production-image question above.