tyler/route-commerce
1
0
Fork 1
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

docs: correct MEMORY.md hosting reference (Gitea, not Vercel)
Deploy to route.crispygoat.com / deploy (push) Successful in 3m50s
Details

Browse Source
This commit is contained in:
Nora
2026-07-03 14:44:42 -06:00
parent fc70344dab
commit 178b85a9da
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MEMORY.md
+4 -2
View File
@@ -688,12 +688,14 @@ rows to a configured sheet. Config UI lives in
- `SMARTSHEET_CRON_SECRET` — optional bearer for the cron route. - `SMARTSHEET_CRON_SECRET` — optional bearer for the cron route.
- `SMARTSHEET_SYNC_TIMEOUT_MS` — optional, default 8000. - `SMARTSHEET_SYNC_TIMEOUT_MS` — optional, default 8000.
**Migration push (Vercel deploy + manual):** **Migration push (Gitea deploy + manual):**
```bash ```bash
npm run migrate:one 93 # pushes 0093_water_smartsheet_sync.sql npm run migrate:one 93 # pushes 0093_water_smartsheet_sync.sql
``` ```
Then provision the encryption key in Vercel dashboard: Then provision the encryption key in **Gitea repository secrets**
(`Settings → Secrets and variables → Actions → Secrets`):
`SMARTSHEET_TOKEN_ENC_KEY` (paste the `openssl rand -base64 32` output). `SMARTSHEET_TOKEN_ENC_KEY` (paste the `openssl rand -base64 32` output).
Optionally also set `SMARTSHEET_CRON_SECRET`.
**Rollback story:** **Rollback story:**
1. Remove the cron entry from `vercel.json`. 1. Remove the cron entry from `vercel.json`.