audio streaming app
plyr.fm
fix: add custom domain CORS support for plyr.fm (#79)
* docs: add custom domain (plyr.fm) to deployment documentation
- updated CORS configuration to support plyr.fm and www.plyr.fm
- documented FRONTEND_CORS_ORIGIN_REGEX in production secrets
- staging doesn't need custom CORS since it only uses cloudflare preview URLs
* docs: show exact production CORS regex (without localhost)
authored by
nate nowack
and committed by
GitHub
361af0f1
5883ad75
+3
-2
+3
-2
docs/deployment/environments.md
+3
-2
docs/deployment/environments.md
···
58
58
**frontend**:
59
59
- cloudflare pages production environment serves `main` branch
60
60
- uses production environment with `PUBLIC_API_URL=https://relay-api.fly.dev`
61
-
- available at `https://relay-4i6.pages.dev`
61
+
- available at `https://plyr.fm` / `https://www.plyr.fm` (custom domain) and `https://relay-4i6.pages.dev`
62
62
63
63
**creating a release**:
64
64
```bash
···
69
69
or via github UI: releases → draft new release → create tag → publish
70
70
71
71
**testing**:
72
-
- frontend: `https://relay-4i6.pages.dev`
72
+
- frontend: `https://plyr.fm` or `https://relay-4i6.pages.dev`
73
73
- backend: `https://relay-api.fly.dev/docs`
74
74
- database: `relay` (neon)
75
75
- storage: `relay` (r2)
···
114
114
**production secrets** (already configured):
115
115
- same structure but with production URLs and database
116
116
- `ATPROTO_APP_NAMESPACE` → not set (defaults to `app.relay`)
117
+
- `FRONTEND_CORS_ORIGIN_REGEX` → `^https://(([a-z0-9]+\.)?relay-4i6\.pages\.dev|(www\.)?plyr\.fm)$` (custom domain + cloudflare pages)
117
118
- additional: `NOTIFY_BOT_HANDLE`, `NOTIFY_BOT_PASSWORD`, `NOTIFY_ENABLED`
118
119
119
120
**local dev (.env)**: