document production migrations

This commit is contained in:
Yisroel Baum 2026-07-31 10:55:26 +03:00
parent 3e02a83dd4
commit 99ceeff5b8
Signed by: yisroelbaum
GPG key ID: 0FA60884F75520A9

View file

@ -40,11 +40,14 @@ intentionally omitted here - update this section as entities land.
## Migrations ## Migrations
- This project is not in production. By default, schema changes should update - This project is in production. Never edit, delete, rename, or reorder an
the relevant create-table migration so migrations describe the current desired existing migration file. Every schema change must use a new forward
schema from scratch. migration.
- Do not add alter-table or data-backfill migrations unless the user explicitly - Production migrations must preserve existing data, include any required
asks for production-style migration safety. backfill, and define a safe rollback.
- Plan schema changes for the deployment order and for compatibility between
the old and new application versions. Use expand/backfill/contract sequencing
when a single compatible migration is not safe.
- Put seed data in seeders, not migrations. - Put seed data in seeders, not migrations.
## PHP rules ## PHP rules