fix(emex): ship runtime scripts/ in prod image and forward chromium executable path #25
Reference in New Issue
Block a user
Delete Branch "fix-emex-scraper-prod-image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two prod-image fixes — EMEX leaf parts have been silently empty for users.
scripts/emex-vin-scraper.jswas never copied to the production image — Dockerfile production stage cherry-picks dist/drizzle/start.sh only. EmexService.doInitialize fails withScraper file not found at: /app/scripts/...on every leaf request.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATHenv var is consumed only byplaywright install, not at runtime. Forward it explicitly tochromium.launch()so Alpine prod image uses the system chromium at/usr/bin/chromium-browserinstead of looking for the missing bundled headless-shell.Repro: VIN
NLAES75204W300895(Honda Civic, emex-decoded) → any leaf category showed0 parça listeleniyor. Root cause traced via prod api logs (Scraper file not found at: /app/scripts/emex-vin-scraper.js).