lronetto/wedding-app
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: pin R2 endpoint and public URL in wrangler vars

Browse Source 
Now that the bucket and r2.dev subdomain are provisioned, commit
the URLs as wrangler [vars] so deploys are reproducible without
relying on dashboard-managed plain-text variables. Only the access
key and secret remain dashboard-only secrets.

https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL
This commit is contained in:
Claude 2026-05-04 02:01:12 +00:00
parent 11a81975ff
commit 4f85dd8721
No known key found for this signature in database
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
apps/web/wrangler.toml
View File

@ -25,10 +25,11 @@ PUBLIC_BASE_URL = "https://stefanieeleandro.pages.dev"
S3_REGION = "auto" S3_REGION = "auto"
S3_BUCKET = "wedding-media" S3_BUCKET = "wedding-media"
S3_FORCE_PATH_STYLE = "false" S3_FORCE_PATH_STYLE = "false"
# S3_ENDPOINT, S3_PUBLIC_BASE_URL, CF_ACCESS_TEAM, CF_ACCESS_AUD are S3_ENDPOINT = "https://04cc83318332b325076a71c8db5e6c42.r2.cloudflarestorage.com"
# set after Cloudflare config (see deploy notes). S3_PUBLIC_BASE_URL = "https://pub-e29e475661ee460c99ba6ea01cf26a7c.r2.dev"
# CF_ACCESS_TEAM, CF_ACCESS_AUD are set after the Cloudflare Access app is created.
# #
# Secrets (set via `wrangler secret put <NAME>` or via the dashboard): # Secrets (set via dashboard or `wrangler secret put`):
# S3_ACCESS_KEY_ID # S3_ACCESS_KEY_ID
# S3_SECRET_ACCESS_KEY # S3_SECRET_ACCESS_KEY
# TURNSTILE_SECRET # TURNSTILE_SECRET