Read photos from the datacenterbingo-photos bucket

The photos moved out of asxpio's invoice bucket into their own (storage
repo); keys are unchanged.

Assisted-by: Claude:opus-5

.env.example

@@ -3,7 +3,7 @@ BINGO_HOST=localhost
 DATABASE_URL=postgres://bingo:change-me@localhost:5432/asxpio
 S3_ENDPOINT=http://localhost:9000
 S3_REGION=us-east-1
-S3_BUCKET=asxpio-invoices
+S3_BUCKET=datacenterbingo-photos
 S3_ACCESS_KEY=change-me
 S3_SECRET_KEY=change-me
 INDEXNOW_KEY=

.forgejo/workflows/deploy.yaml

@@ -122,7 +122,7 @@ jobs:
             DATABASE_URL=postgres://bingo:${BINGO_DB_PASSWORD}@postgres:5432/asxpio
             S3_ENDPOINT=http://minio:9000
             S3_REGION=us-east-1
-            S3_BUCKET=asxpio-invoices
+            S3_BUCKET=datacenterbingo-photos
             S3_ACCESS_KEY=${BINGO_S3_ACCESS_KEY}
             S3_SECRET_KEY=${BINGO_S3_SECRET_KEY}
             INDEXNOW_KEY=${INDEXNOW}

CLAUDE.md

@@ -9,8 +9,8 @@ deploy); `github.com/asxpi/datacenterbingo` is a push mirror.
 
 Content is edited in the asxp.io admin (`/admin/bingo`, repo `asxpio`:
 `lib/bingo.rb`, `lib/bingo_admin.rb`). Both apps use the same Postgres tables
-(`bingo_datacenters`, `bingo_incidents`) and the photos under `bingo/` in
-asxpio's MinIO bucket.
+(`bingo_datacenters`, `bingo_incidents`) and the photos under `bingo/` in the
+`datacenterbingo-photos` bucket (asxpio's admin uploads them there).
 
 - **asxpio owns the schema.** Migrations live there. After it adds a
   bingo migration, refresh `test/schema.sql` (instructions in its header)
@@ -21,7 +21,7 @@ asxpio's MinIO bucket.
   seeding, `guess_provider`) stays in asxpio. Keep shared parts in step:
   `PROVIDERS`, `Board`, and model methods.
 - Prod uses a read-only DB role `bingo` (SELECT on the two tables) and a
-  MinIO user limited to `s3:GetObject` on `asxpio-invoices/bingo/*`. Both
+  MinIO user limited to `s3:GetObject` on `datacenterbingo-photos`. Both
   are provisioned by the `storage` repo (`init/`), from the same
   `BINGO_*` secrets set on both repos.