CROP
ProjectsCROP Frontend

McHale Media Drops

Location: Updated: 2025-11-07

McHale Media Drops

Location: data/manufacturers/mchale/media Updated: 2025-11-07

Files

FileDescription
storage-manifest.jsonCondensed manifest consumed by the front-end when resolving preview + 360° assets. Keys match the McHale vendor codes used by the catalog.
storage-media-catalog.jsonFull export from Google Cloud Storage containing per-asset metadata, checksums, and counts. Useful for audits and tooling.
storage-all-media-urls.txtPlain-text URL list for quick diffing or to seed downstream syncing jobs.

Refresh workflow

  1. Ensure you have access to the McHale bucket (gs://crop_parts/McHale).
  2. Run the extraction script to pull the latest inventory:
    bun scripts/extract-mchale-media-urls.ts \
      --bucket gs://crop_parts/McHale \
      --out data/manufacturers/mchale/media/storage-all-media-urls.txt
  3. Generate the JSON artifacts for the app layer:
    bun scripts/generate-mchale-storage-urls.ts
    The script reads the URL list, groups assets by part, and writes both storage-manifest.json and storage-media-catalog.json.
  4. Commit the refreshed files and mention the timestamp in your PR description.

Consumers

  • lib/utils/image-url-builder.ts builds fallback URLs but prefers entries from this manifest when present.
  • lib/search-service/adapters.ts merges API media data with local manifests to guarantee every part has at least one image/360 reference.

Please avoid storing environment secrets in these files; they ship to the client in certain views.

On this page