create-snagset 0.1.20 → 0.1.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -82,7 +82,14 @@ gives you a role without the bypass.
82
82
 
83
83
  ## Deploy it
84
84
 
85
- **Vercel.** `vercel.json` and `api/index.js` are here already. The
85
+ **Vercel.** `vercel.json` and `api/index.js` are here already. **Set
86
+ `regions` in `vercel.json` to the region your database is in** — it says
87
+ `iad1` (Washington, Vercel's default) until you do. Functions on another
88
+ continent from the database make every page wait on that distance, several
89
+ times over. Neon `eu-west-2` or Supabase `eu-west-2` → `lhr1`; `eu-central-1`
90
+ → `fra1`; `us-east-1` → `iad1`; `us-west-2` → `pdx1`; `ap-southeast-1` →
91
+ `sin1`; `ap-northeast-1` → `hnd1`; `ap-southeast-2` → `syd1`. The dashboard
92
+ says so if they differ. The
86
93
  `rewrites` entry is load-bearing: without it Vercel's filesystem router serves
87
94
  only `/api/index` and 404s `/`, `/snag.js` and the cron's own path. Keep the
88
95
  file free of comment keys — Vercel's schema rejects them. Set `DATABASE_URL`
@@ -1,5 +1,8 @@
1
1
  {
2
2
  "$schema": "https://openapi.vercel.sh/vercel.json",
3
+ "regions": [
4
+ "iad1"
5
+ ],
3
6
  "rewrites": [
4
7
  {
5
8
  "source": "/(.*)",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-snagset",
3
- "version": "0.1.20",
3
+ "version": "0.1.22",
4
4
  "private": false,
5
5
  "type": "module",
6
6
  "description": "Scaffold your own Snagset instance. One command, Postgres included, one variable to fill in.",