asxpi/datacenterbingo
asxpi/datacenterbingo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Read photos from the datacenterbingo-photos bucket
All checks were successful
Build and Deploy to Production / test (push) Successful in 17s
Details
Build and Deploy to Production / build (push) Successful in 50s
Details
Build and Deploy to Production / deploy (push) Successful in 36s
Details

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

Assisted-by: Claude:opus-5
This commit is contained in:
Sergei Poljanski 2026-10-12 04:09:01 +04:00
commit 9c8606fbac
Signed by: asxpi
GPG key ID: 4F8851660FA4121B
3 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
CLAUDE.md
View file

@ -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.