Area: CLI / Build
This area records the preview-relevant source and manifest rationale for
J01-98.
It describes only the narrow path that SCRUM Sprint 1 needs for the public
preview migration.
Pipeline and Phase Model
- The CLI executes phases directly:
cli <phase> <pipeline> [args]. - For the preview path,
setup,build,runtime, anddeploymatter most. - Config loading moves from versioned defaults to local overrides and then into
the compiled runtime file
var/config/config.php.
Manifest Rules
src/resources/config/config.manifest.yamldefines variable groups, allowed areas, and required values per pipeline/phase.IP_SALTis limited tosystem,local, andfile, so it may not come from arbitrary other sources.- Deploy values such as
FTP_HOST,FTP_USER, andFTP_PASSare restricted to safer source types. APP_BASE_PATHandFTP_SERVER_DIRexplain the visible preview target without hidden special logic in the doc path.
Planned Manifest Model from J01-105
Issue J01-105 sharpens the manifest model editorially:
variablesstays the parameter catalog in the app repo.pipelinescarries the rule layer.- The planned levels are
pipelines.global,pipelines.common.<phase>, andpipelines.<pipeline>.<phase>. - The planned syntax may reference full areas or partial areas.
- After expansion there must be no overlap between
global,common, and the concrete pipeline.
The full derivation of this thin target model is recorded on the public issue page for J01-105.
Public Preview Path
The narrow preview path for J01-98 is:
php bin/cli config lint <pipeline>checks that the manifest and source logic fit together.php bin/cli setup previewprepares the preview run.php bin/cli build previewproduces the deliverable state.- Runtime uses only the compiled config and no direct
getenv()lookups.
Boundary
- This page explains the technical shape for
J01-31. - Detailed operating rules for the local Pages preview stay in the preview runbook.
- Runtime-related stability aspects stay in Area: HTTP runtime.
- Everything beyond the active preview sprint stays outside
J01-98.