Developer
41f9427224
When a manifest mount target uses ~/{{WORKSPACE_NAME}}, the Dockerfile was
building a literal directory named {{WORKSPACE_NAME}} into the image and
creating a broken /workspace symlink. The runtime mount then created the
correct repo-named folder alongside the placeholder folder.
- Only create static mount target directories in the Dockerfile; skip any
target containing {{WORKSPACE_NAME}}
- Only create the /workspace compatibility symlink at image-build time when
the workspace name is known; otherwise let the entrypoint create it from
the WORKSPACE_NAME environment variable
- Update unit tests to cover both build-time workspace names and runtime
placeholders
Quality gates:
- pytest tests/unit: 211 passed
- ruff: clean on changed files
- mypy: clean on changed files
19 lines
295 B
Markdown
19 lines
295 B
Markdown
# apps
|
|
dir: apps
|
|
|
|
index: apps/.pi-map.index.md
|
|
|
|
## role
|
|
Contains the main deployable application modules that compose the complete system.
|
|
## files
|
|
## arch
|
|
Monolithic or modular monolith architecture with domain-separated application boundaries.
|
|
## tags
|
|
-
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|