g1t/services/pages/wrangler.jsonc
| 1 | { |
| 2 | "$schema": "../../node_modules/wrangler/config-schema.json", |
| 3 | "name": "g1t-pages", |
| 4 | "account_id": "1e6f2cffa3f445920836e8ebe446bb58", |
| 5 | "compatibility_date": "2026-09-26", |
| 6 | "main": "./src/index.ts", |
| 7 | "workers_dev": false, |
| 8 | // Every app on g1t.page. The wildcard needs a proxied DNS record (`*`, |
| 9 | // AAAA 100::) on the zone; the apex, which says what g1t.page is, is a |
| 10 | // custom domain, whose record Cloudflare makes. |
| 11 | // |
| 12 | // `*/*` is for custom domains: Cloudflare for SaaS sends each custom |
| 13 | // hostname's traffic through the g1t.page zone, and this route is what |
| 14 | // brings it here. Custom hostnames point at the fallback origin, |
| 15 | // domains.g1t.page (a proxied AAAA 100::), set up once by |
| 16 | // scripts/setup-custom-domains.sh. |
| 17 | "routes": [ |
| 18 | { "pattern": "*.g1t.page/*", "zone_name": "g1t.page" }, |
| 19 | // Custom domains (Cloudflare for SaaS is on for the zone). |
| 20 | { "pattern": "*/*", "zone_name": "g1t.page" }, |
| 21 | { "pattern": "g1t.page", "custom_domain": true } |
| 22 | ], |
| 23 | // The apps, uploaded by the deployments service. |
| 24 | "dispatch_namespaces": [{ "binding": "APPS", "namespace": "g1t-deployments" }], |
| 25 | // Custom domains: hostname to app, written by the deployments service. |
| 26 | "kv_namespaces": [{ "binding": "DOMAINS", "id": "14bc5c233d4c46a5bbf23b5367cce5fd" }], |
| 27 | "observability": { "enabled": true } |
| 28 | } |