Update MineGeo domain and harden process supervision
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 5m57s
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 5m57s
This commit is contained in:
@@ -78,7 +78,7 @@ variables in Vercel:
|
||||
- `LINEAR_PROJECT_ID`: optional project UUID or Linear project identifier.
|
||||
|
||||
Enable **Comment and Issue** events on the team webhook and set its URL to
|
||||
`https://minegeo.vercel.app/api/support/linear`. Redeploy after saving environment
|
||||
`https://minegeo.site/api/support/linear`. Redeploy after saving environment
|
||||
variables. Keys stay server-side and must never be pasted into issue descriptions,
|
||||
client configuration, or source uploads.
|
||||
|
||||
@@ -96,7 +96,7 @@ for durable timers. No additional secret or cron is needed.
|
||||
Validation: `npm test`, `npm run typecheck`, `npm run build`, and
|
||||
`node scripts/test-bug-reports-sql.mjs` (uses the isolated PGlite installation under
|
||||
`.data/sql-verification`, as the other SQL verification scripts do).
|
||||
`node scripts/test-bug-retention-http.mjs https://minegeo.vercel.app` verifies
|
||||
`node scripts/test-bug-retention-http.mjs https://minegeo.site` verifies
|
||||
the deployed flow with a clearly labeled temporary report and screenshot. It
|
||||
checks ownership, Done synchronization, the three-day deadline, and deletion
|
||||
from both systems by advancing only that test report's deadline. The fixture ID
|
||||
|
||||
Reference in New Issue
Block a user