Keep run as ignored local checkout

This commit is contained in:
npc0-hue
2026-07-14 18:03:12 +08:00
parent a57a5dbfcf
commit 4ba5bd6971
8 changed files with 22 additions and 22 deletions
@@ -8,17 +8,17 @@ Browser-side code can still expose platform APIs for run endpoints, jobs, logs,
## Local Development
Local debug workflows use `RUN_REPO_DIR` to find an external run checkout. The default points to `../run`, matching a sibling clone beside this repository:
Local debug workflows use `RUN_REPO_DIR` to find an external run checkout. The default points to `./run`, an ignored nested checkout inside this repository:
```bash
git clone git@git.npc0.com:admin343/run.git ../run
git clone git@git.npc0.com:admin343/run.git run
```
If `RUN_REPO_DIR` is missing or does not contain a run `go.mod`, local debug scripts fail with a clear message instead of assuming `browser/run`.
If `RUN_REPO_DIR` is missing or does not contain a run `go.mod`, local debug scripts fail with a clear setup message.
## Docker Compose
The compose file keeps the run service for all-in-one local deployment, but its build context points at `${RUN_REPO_DIR:-../run}` and uses the external repository's `Dockerfile`.
The compose file keeps the run service for all-in-one local deployment, but its build context points at `${RUN_REPO_DIR:-./run}` and uses the external repository's `Dockerfile`.
## Structure Validation
@@ -10,7 +10,7 @@ The browser repository SHALL NOT store the machine-side run executor source tree
#### Scenario: Local debug needs a run worker
- **WHEN** a local debug or Docker workflow needs to start run
- **THEN** it MUST locate run through `RUN_REPO_DIR` or a documented sibling checkout
- **THEN** it MUST locate run through `RUN_REPO_DIR` or the documented ignored nested checkout
- **AND** it MUST fail with a clear setup message when the external checkout is missing
#### Scenario: Structure validation runs