62f67ba809
Add a same-origin API proxy route at `/api/pb/[...path]` to forward requests to PocketBase, resolving mixed content blocking issues when the Next.js app is served over HTTPS but PocketBase uses HTTP. Update environment variables to separate the public client-facing URL and internal server-side PocketBase upstream URL, and update all env config examples and deployment files to match the new setup. Clean up the app paths manifest to include the new API route and remove a stale entry.
14 lines
766 B
Text
14 lines
766 B
Text
# PB URL the browser talks to. In production (HTTPS) this should be the
|
|
# same-origin proxy: /api/pb. In dev (localhost HTTP) you can point
|
|
# straight at PB on http://127.0.0.1:8090 or your remote instance.
|
|
NEXT_PUBLIC_POCKETBASE_URL=/api/pb
|
|
# (Or, for dev with a remote PB:)
|
|
# NEXT_PUBLIC_POCKETBASE_URL=http://pocketbase-zinlbpsext2ro0lgb2558vfy.169.239.180.130.sslip.io
|
|
|
|
# Server-side upstream for the /api/pb proxy. Only used by the proxy route
|
|
# itself; the client never sees this. Falls back to a sane default.
|
|
PB_INTERNAL_URL=http://pocketbase-zinlbpsext2ro0lgb2558vfy.169.239.180.130.sslip.io
|
|
|
|
# Superuser auth token — used by server-side admin operations (migrations, seed).
|
|
# Optional for runtime; required only for the scripts/ helpers.
|
|
PB_ADMIN_TOKEN=
|