viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

tripit: enable live flight-fare scrape via shared chrome-service CDP

Browse source 
Sets FARE_PROVIDER=playwright + FARE_CDP_URL on the tripit deployment so the planning workspace's flight_fare cells auto-fetch live Google Flights quotes through the existing in-cluster headed browser (tripit issue #18, ADR-0007 — rate-limited, cached, degrades to manual entry). Viktor asked to complete the trip-planning tickets; this is the infra leg of the fare-scrape slice. Docs: chrome-service architecture + service catalog updated (tripit is now the second active CDP caller; catalog's legacy :3000 WS pool line corrected to CDP :9222). HOLD-ORDER NOTE: pushed only after the tripit image containing FareMode.playwright rolled out (older images crash-loop on the unknown enum).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-06-11 14:23:53 +00:00
parent bd60c3d5e0
commit 980ec55418
3 changed files with 18 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/architecture/chrome-service.md
View file

@ -10,9 +10,14 @@ serves two distinct populations:
`chromium.connect_over_cdp("http://chrome-service.chrome-service.svc:9222")`
to drive a real browser when upstream anti-bot trips a headless one
(`disable-devtool.js` redirect-to-google trap, `navigator.webdriver`
checks, console-clear timing tricks). The only currently-active
in-cluster caller is the `chrome-service-snapshot-harvester` CronJob;
the `stacks/f1-stream/files/backend/playback_verifier.py` +
checks, console-clear timing tricks). Currently-active in-cluster
callers: the `chrome-service-snapshot-harvester` CronJob, and
**tripit's `PlaywrightFareProvider`** (since 2026-06-11, tripit issue
#18 / ADR-0007) — the flight-fare scrape connects per quote, opens a
fresh incognito context, scrapes Google Flights, and closes the
context; rate-limited to one attempt per 30s with a 6h fare cache, so
browser load is negligible. The
`stacks/f1-stream/files/backend/playback_verifier.py` +
`chrome_browser.py` tree is a vestigial design — the deployed
f1-stream image (built from `github.com/ViktorBarzin/f1-stream`)
does not use this code path.