management: product image upload to R2 #44

New issue

Closed

opened 2026-08-27 06:35:52 +00:00 by yuris · 0 comments

yuris commented

2026-08-27 06:35:52 +00:00

Owner

Every mockup renders products at a 1:1 contained aspect ratio, and apps/store/next.config.ts sets images.unoptimized — so whatever URL lands in inventory.images is served verbatim. Today both inventory forms accept pasted URL strings only (add-inventory-modal.tsx, inventory-edit-form.tsx), and scripts/seed-demo.mts uses placehold.co. There is no upload path, so real product photos depend on the operator hosting files somewhere else. The design cannot ship with real imagery until this exists.

Change

lib/storage/r2.ts already has the whole mechanism in uploadReceipt(file, "order" | "purchase") — S3 client, MIME allow-list, size caps, ${R2_PUBLIC_URL}/${key} return. Generalise the key prefix and kind rather than writing a second uploader: accept a product kind writing to products/{YYYY}/{MM}/{uuid}{ext}, keep receipts on their existing prefix so nothing already stored moves. Images only for this kind — no PDF branch, and hold the 5 MB image cap.

Route: extend app/api/[[...route]]/uploads.ts, whose type is currently restricted to order|purchase.
Client: extend lib/uploads.ts, then replace the URL-row inputs in both inventory forms with a file picker that appends the returned public URL into images. Keep manual URL entry working — items already reference external URLs.
MCP: lib/mcp/tools/images.ts gains the product kind alongside upload_receipt.

Acceptance

An operator uploads a photo in the stok form and the item renders it on the storefront after the next deploy, with no external hosting. Receipt uploads are byte-for-byte unaffected: same prefix, same caps, same PDF handling. A non-image file and an oversized file are both rejected with a readable message. Cover the kind→prefix mapping and the rejection paths in vitest.

Every mockup renders products at a 1:1 contained aspect ratio, and `apps/store/next.config.ts` sets `images.unoptimized` — so whatever URL lands in `inventory.images` is served verbatim. Today both inventory forms accept **pasted URL strings only** (`add-inventory-modal.tsx`, `inventory-edit-form.tsx`), and `scripts/seed-demo.mts` uses `placehold.co`. There is no upload path, so real product photos depend on the operator hosting files somewhere else. The design cannot ship with real imagery until this exists. ### Change `lib/storage/r2.ts` already has the whole mechanism in `uploadReceipt(file, "order" | "purchase")` — S3 client, MIME allow-list, size caps, `${R2_PUBLIC_URL}/${key}` return. Generalise the key prefix and kind rather than writing a second uploader: accept a `product` kind writing to `products/{YYYY}/{MM}/{uuid}{ext}`, keep receipts on their existing prefix so nothing already stored moves. Images only for this kind — no PDF branch, and hold the 5 MB image cap. - Route: extend `app/api/[[...route]]/uploads.ts`, whose `type` is currently restricted to `order|purchase`. - Client: extend `lib/uploads.ts`, then replace the URL-row inputs in both inventory forms with a file picker that appends the returned public URL into `images`. Keep manual URL entry working — items already reference external URLs. - MCP: `lib/mcp/tools/images.ts` gains the product kind alongside `upload_receipt`. ### Acceptance An operator uploads a photo in the stok form and the item renders it on the storefront after the next deploy, with no external hosting. Receipt uploads are byte-for-byte unaffected: same prefix, same caps, same PDF handling. A non-image file and an oversized file are both rejected with a readable message. Cover the kind→prefix mapping and the rejection paths in `vitest`.

yuris referenced this issue

2026-08-27 08:02:58 +00:00

feat(catalog): schema v3 — fitment, oemNumbers, priceUpdatedAt, availability tri-state #53

yuris referenced this issue

2026-08-27 12:58:39 +00:00

feat(management): edit item name and sell price from the dashboard #56

yuris referenced this issue from a pull request that will close it,

2026-08-27 18:21:22 +00:00

feat(management): product image upload to R2 from both stok forms #62

yuris referenced this issue

2026-08-27 19:53:46 +00:00

feat(management): product image upload to R2 from both stok forms #62