Developer
47de2a0133
The previous ordering checked SUDO before checking if the process was already running as root. When Docker starts the container with a non-root user, SUDO may be empty, but the real fix is that the entrypoint should try root first (e.g. when the image is started as root) and only then fall back to sudo. - Reorder symlink creation logic: root first, then sudo, then best-effort - Update unit test to assert root is checked before sudo Quality gates: - pytest tests/unit: 208 passed - ruff: clean on changed files - mypy: clean on changed files
19 lines
415 B
Markdown
19 lines
415 B
Markdown
# apps
|
|
dir: apps
|
|
|
|
index: apps/.pi-map.index.md
|
|
|
|
## role
|
|
Contains the deployable application entry points and executable configurations for the project.
|
|
## files
|
|
## arch
|
|
Multi-app workspace structure with separate application boundaries, likely following micro-frontend or modular monolith patterns where each sub-directory represents an independent deployable unit.
|
|
## tags
|
|
-
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|