wedding-app/apps/web/wrangler.toml

name = "stefanieeleandro"
main = "src/worker.ts"
compatibility_date = "2026-04-01"
compatibility_flags = ["nodejs_compat"]

[assets]
directory = "./dist"
binding = "ASSETS"
not_found_handling = "single-page-application"
run_worker_first = ["/api/*"]

[[d1_databases]]
binding = "DB"
database_name = "wedding-db"
database_id = "81fac13f-00b2-49ec-b7df-bde036849e70"
migrations_dir = "../api/migrations"

[[r2_buckets]]
binding = "MEDIA"
bucket_name = "wedding-media"

[vars]
COUPLE_NAMES = "Stefanie & Leandro"
PUBLIC_BASE_URL = "https://stefanieeleandro.pages.dev"
S3_REGION = "auto"
S3_BUCKET = "wedding-media"
S3_FORCE_PATH_STYLE = "false"
# S3_ENDPOINT, S3_PUBLIC_BASE_URL, CF_ACCESS_TEAM, CF_ACCESS_AUD are
# set after Cloudflare config (see deploy notes).
#
# Secrets (set via `wrangler secret put <NAME>` or via the dashboard):
#   S3_ACCESS_KEY_ID
#   S3_SECRET_ACCESS_KEY
#   TURNSTILE_SECRET
#   ALLOWED_ADMIN_EMAILS
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00			`name = "stefanieeleandro"`
refactor: migrate web app to Workers + Static Assets format The Cloudflare project was created as a Workers Build (the new unified format), so the legacy Pages config (pages_build_output_dir, functions/api/[[path]].ts) does not deploy. Switch to the modern shape: a worker entry point that delegates to the Hono app for /api/* and falls through to the [assets] binding for everything else, with SPA fallback for client-side routes. Build output (apps/web/dist) and bindings (D1, R2, env vars) are unchanged. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-03 21:57:28 -03:00			`main = "src/worker.ts"`
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00			`compatibility_date = "2026-04-01"`
			`compatibility_flags = ["nodejs_compat"]`
refactor: migrate web app to Workers + Static Assets format The Cloudflare project was created as a Workers Build (the new unified format), so the legacy Pages config (pages_build_output_dir, functions/api/[[path]].ts) does not deploy. Switch to the modern shape: a worker entry point that delegates to the Hono app for /api/* and falls through to the [assets] binding for everything else, with SPA fallback for client-side routes. Build output (apps/web/dist) and bindings (D1, R2, env vars) are unchanged. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-03 21:57:28 -03:00
			`[assets]`
			`directory = "./dist"`
			`binding = "ASSETS"`
			`not_found_handling = "single-page-application"`
			`run_worker_first = ["/api/*"]`
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00
			`[[d1_databases]]`
			`binding = "DB"`
			`database_name = "wedding-db"`
Atualizar o wrangler.toml 2026-05-02 13:31:53 -03:00			`database_id = "81fac13f-00b2-49ec-b7df-bde036849e70"`
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00			`migrations_dir = "../api/migrations"`

			`[[r2_buckets]]`
			`binding = "MEDIA"`
			`bucket_name = "wedding-media"`

			`[vars]`
			`COUPLE_NAMES = "Stefanie & Leandro"`
			`PUBLIC_BASE_URL = "https://stefanieeleandro.pages.dev"`
			`S3_REGION = "auto"`
			`S3_BUCKET = "wedding-media"`
			`S3_FORCE_PATH_STYLE = "false"`
			`# S3_ENDPOINT, S3_PUBLIC_BASE_URL, CF_ACCESS_TEAM, CF_ACCESS_AUD are`
refactor: migrate web app to Workers + Static Assets format The Cloudflare project was created as a Workers Build (the new unified format), so the legacy Pages config (pages_build_output_dir, functions/api/[[path]].ts) does not deploy. Switch to the modern shape: a worker entry point that delegates to the Hono app for /api/* and falls through to the [assets] binding for everything else, with SPA fallback for client-side routes. Build output (apps/web/dist) and bindings (D1, R2, env vars) are unchanged. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-03 21:57:28 -03:00			`# set after Cloudflare config (see deploy notes).`
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00			`#`
refactor: migrate web app to Workers + Static Assets format The Cloudflare project was created as a Workers Build (the new unified format), so the legacy Pages config (pages_build_output_dir, functions/api/[[path]].ts) does not deploy. Switch to the modern shape: a worker entry point that delegates to the Hono app for /api/* and falls through to the [assets] binding for everything else, with SPA fallback for client-side routes. Build output (apps/web/dist) and bindings (D1, R2, env vars) are unchanged. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-03 21:57:28 -03:00			# Secrets (set via `wrangler secret put <NAME>` or via the dashboard):
chore: scaffold Cloudflare Pages monorepo for wedding photos app Set up pnpm workspaces with three packages: a shared Zod-schema package, a Hono-based API exported as a library, and a Vite/React/ Tailwind frontend that mounts the API via Cloudflare Pages Functions. Storage is abstracted behind an S3-compatible provider so the project can migrate from R2 to a self-hosted MinIO without code changes. https://claude.ai/code/session_01TPBqgcSJMppgrpiq7fLywL 2026-05-01 20:30:50 -03:00			`# S3_ACCESS_KEY_ID`
			`# S3_SECRET_ACCESS_KEY`
			`# TURNSTILE_SECRET`
			`# ALLOWED_ADMIN_EMAILS`