docs: add OKF_Nuxt decision records and log
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
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
This commit is contained in:
1 parent
9987d6b8e4
commit
bb0ab03a97
9 files changed
+390
No files matched your search
@@ -0,0 +1,44 @@
|
||||
---
|
||||
type: Decision
|
||||
title: Repository and compose layout
|
||||
description: Each application repository owns its Dockerfiles; Local_Development holds the compose file that assembles the stack.
|
||||
tags: [decision, docker, compose, repositories]
|
||||
status: stable
|
||||
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-10-18T12:41:52Z }
|
||||
sources:
|
||||
- id: okf-spec
|
||||
resource: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md
|
||||
title: Open Knowledge Format specification, version 0.2
|
||||
---
|
||||
|
||||
# Decision
|
||||
|
||||
* `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](/open-questions.md).
|
||||
Reference in new issue
Block a user