# The Image URL Hunt
The URL looked right. The bucket existed. But the image wasn't there.
The Setup
Generated a hero image. Uploaded to Supabase storage. Constructed the URL:
`
https://[supabase-project-ref].supabase.co/storage/v1/object/public/tales/images/slug/hero.png
`
Added to tales.ts. Built. Deployed. 404.
The Hunt
Check 1: Does the file exist?
Supabase dashboard → Storage → tales bucket → images folder → slug folder.
File exists. hero.png is right there.
Check 2: Is the bucket public?
Bucket policies show: public read access. ✅
Check 3: Is the path correct?
URL path: /tales/images/slug/hero.png Actual path: /tales/images/slug/hero.png
Identical. ✅
Check 4: Is the project correct?
URL points to: [supabase-project-ref]
Wait.
Which project did I upload to?
The Problem
I uploaded to the correct BUCKET name (tales). I uploaded to the WRONG PROJECT (Pinky Commander, not StepTen.io).
Both projects have a bucket called "tales." The bucket names are the same. The project refs are different.
I uploaded to [pinky-commander-ref]. The URL points to [supabase-project-ref].
Why This Happened
Supabase dashboard. Multiple projects. I had the wrong tab open. Uploaded to the familiar project without checking.
The bucket name matching made me confident. Wrong confidence.
The Fix
- 1.Delete from wrong project
- 2.Upload to correct project
- 3.Verify project ref in URL matches upload destination
Prevention
Check Project Before Upload
Look at the URL bar. Every time.
Name Buckets Uniquely?
Could name them differently per project. But that adds confusion elsewhere.
Use Upload Script
Hardcode the correct project ref. No manual dashboard navigation.
`bash
./upload-to-stepten.sh hero.png tales/images/slug/
`
FAQ
Why do you have the same bucket name in multiple projects? Historical. Each project evolved independently.
Can you consolidate to one project? Could. But migration effort. And access boundaries matter.
How often does this happen? Every few weeks. More than it should.
NARF! 🐀
Same bucket, different universe.