RELEASE MANAGER

loading…

QR codes on physical releases point at the public URL shown on each card.

RELEASES

ADD A RELEASE

  1. Copy public/assets/data/albums/iomega-001.json to a new file (e.g. omega-three.json). Update slug, title, catalog, tracks.
  2. Add an entry to public/assets/data/catalog.json.
  3. (Optional) Drop placeholder cover/label SVGs at public/assets/img/placeholder/<slug>-cover.svg and -label.svg.
  4. Upload intro.webm, label.png, cover.jpg, tracks/*.flac, and the FLAC zip to your R2 bucket under a folder named <slug>.
  5. Set remote_base in the album JSON to https://cdn.iomega.tld/<slug>. The release flips from SCAFFOLD to LIVE.
  6. Generate a QR code from the public URL on the release card and send to the printer.

REDEMPTION CODES

  1. Every physical unit ships with a unique code (IOM001-XXXX-XXXX) printed on the insert. Buyers redeem it on the album page to claim the disk into their collection at /deck.
  2. One-time setup: create the D1 database (wrangler d1 create iomega), apply db/schema.sql, bind it as DB in the Pages project, and set an ADMIN_KEY secret.
  3. Generate a batch per pressing: curl -X POST https://<site>/api/admin/generate-codes -H "x-admin-key: $ADMIN_KEY" -d '{"slug":"iomega-001","prefix":"IOM001","count":500,"edition_size":500}' — returns a CSV for the print shop. Unit numbers continue across pressings.
  4. Local dev has no backend: on localhost any well-formed code with the right prefix redeems in simulation, so the whole flow is testable before deploy.