David/kanban-dev-webapp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kanban-dev-webapp/pocketbase/pb_migrations/README.md
Dave 95346c5c82 docs: Coolify-only setup, and mark pb_migrations as non-executing 
There is one PocketBase instance and it is hosted. Removes the `npm run pb`
script, which started a local server nothing used.

The schema had two apparent sources of truth. scripts/setup-remote.ts is the
one that actually runs; pb_migrations/ only executes on PocketBase server
start, which never happens here. Both now say so, so nobody edits a migration
and believes the schema changed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-16 10:32:26 +02:00

809 B
Raw Blame History

These migrations never run

PocketBase applies files in pb_migrations/ when its own server starts. This project does not start a PocketBase server — it uses one hosted instance on Coolify, and the schema is applied to it over the admin API by scripts/setup-remote.ts.

So every file in this directory is reference only. Editing one changes nothing, anywhere.

To change the schema, edit scripts/setup-remote.ts and run npm run setup-remote.

These files are kept because they are the most readable statement of the schema and its reasoning, and because they are what you would mount into the container if this project ever moves to PocketBase's native migration flow. If you update setup-remote.ts, update these too — but understand that doing so is documentation, not deployment.