Right now datagov-catalog and datagov-harvester can't run locally at the same time out of the box — both default to app port 8080, OpenSearch ports 9200/9600, and DB port 5432/5433, and catalog spins up its own disconnected Postgres/OpenSearch instead of the shared ones harvester actually writes to in every real environment.
This came up while working on #6271 (harvest source report), where catalog links needed a real, running catalog instance to point at and verify against locally.
Already prototyped and confirmed working:
- Remapped catalog's local ports (app, DB, OpenSearch) so both stacks can run side by side
- A docker-compose override that points catalog's local app at harvester's Postgres and OpenSearch instead of running its own, mirroring how they share data in dev/staging/prod
Want a PR that:
- Fixes the default port collisions in datagov-catalog's docker-compose.yml/.env.sample
- Documents (or productizes) the shared-DB/OpenSearch local dev pattern so this isn't something each person has to rediscover
Right now datagov-catalog and datagov-harvester can't run locally at the same time out of the box — both default to app port 8080, OpenSearch ports 9200/9600, and DB port 5432/5433, and catalog spins up its own disconnected Postgres/OpenSearch instead of the shared ones harvester actually writes to in every real environment.
This came up while working on #6271 (harvest source report), where catalog links needed a real, running catalog instance to point at and verify against locally.
Already prototyped and confirmed working:
Want a PR that: