@@ -39,7 +39,7 @@ tests/ # unit/, integration/, verify/
3939site/ # Astro landing page, deployed to GitHub Pages
4040docs/ # SPEC, DATA_PIPELINE, DEVELOPMENT
4141.github/workflows/ # CI; every workflow is listed below
42- Dockerfile, docker-compose.yml # stale, do not build (see Docker)
42+ Dockerfile, docker-compose.yml # API + Postgres, dataset mounted (see Docker)
4343```
4444
4545Routes under ` /v1 ` : ` health ` , ` version ` , ` brands ` , ` socs ` , ` smartphones ` ,
@@ -115,11 +115,19 @@ Smartphones continue to require numeric values for both fields.
115115
116116### Docker
117117
118- ` Dockerfile ` and ` docker-compose.yml ` predate the split from TechAPI and do
119- not work as they are: the Dockerfile copies ` data/ ` and ` scripts/ ` , which no
120- longer exist here, so the image does not build, and the compose file mounts no
121- TechAPI checkout for ` app.seed ` to read. No workflow builds or uses them. Use
122- the Quickstart above; for Postgres, point ` DATABASE_URL ` at your own instance.
118+ The image holds the engine only and expects the dataset at ` /data `
119+ (` TECHAPI_DATA_DIR ` ). ` docker-compose.yml ` starts Postgres and the API, and
120+ mounts ` ../TechAPI/data ` read-only at that path, so clone the two repos side by
121+ side:
122+
123+ ``` text
124+ <parent>/TechEngine # this repo; run `docker compose up --build` here
125+ <parent>/TechAPI # the dataset
126+ ```
127+
128+ The API seeds the database from the mount before it serves, which takes a
129+ while on the full dataset. The image has no git, so record timestamps are the
130+ seed time. No workflow builds or uses these files.
123131
124132## Roadmap
125133
0 commit comments