Docs: job event stream, app-preview routes, migration notes

SERVICE.md documents the /events polling endpoint, the event persistence
model, the in-memory backend's enqueue-202 contract, and the app-preview
route; DEPLOY.md notes the job_events migration and that db:migrate is
journal-tracked/idempotent (with the manual-psql alternative).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Samraaj Bath
2026-07-04 15:16:08 -07:00
co-authored by Claude Fable 5
parent bbe4a5643b
commit c35680eb13
2 changed files with 21 additions and 3 deletions
+9 -1
View File
@@ -16,7 +16,15 @@ Postgres and S3-compatible storage. The recommended OSS-friendly stack:
```bash
DATABASE_URL='postgres://...neon.../ditto_site?sslmode=require' npm run db:migrate
```
Run this on every deploy that changes `packages/db/migrations`.
Run this on every deploy that changes `packages/db/migrations`. Drizzle tracks
applied migrations in the database, so re-running is a no-op for anything
already applied. (Alternatively, apply a single migration by piping its SQL
through `psql`/the Neon CLI — but prefer `db:migrate`, which also records the
journal entry so future runs stay consistent.)
Current migrations: `0000` core tables, `0001` signup tokens,
`0002` `job_events` (structured clone-progress events behind
`GET /v1/clones/:id/events`).
## 2. Blob storage (R2 / S3)