ff b148c0de30 fix: apply missing migrations directly after DB restore ...

Replace the prisma migrate deploy subprocess with a custom
applyMissingMigrations() that reads each migration SQL file and runs it
via prisma.$executeRawUnsafe. This avoids the Prisma CLI aborting when
the restored _prisma_migrations table contains orphaned entries (migration
names that no longer have a corresponding file in the migrations folder).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-17 22:36:35 -04:00

..

.turbo

initial commit

2026-04-04 22:13:55 -04:00

backups

fix: MH eligibility selenium integration and patient data extraction

2026-04-14 22:10:19 -04:00

src

fix: apply missing migrations directly after DB restore

2026-05-17 22:36:35 -04:00

uploads/patient-documents

initial commit

2026-04-04 22:13:55 -04:00

.env

fix: auto-migrate after DB restore and force re-login

2026-05-17 22:31:12 -04:00

.env.example

fix: correct db port, localhost defaults, hashed passwords in seed

2026-04-04 23:30:05 -04:00

package.json

feat: improve backup management, settings UI, and Twilio webhooks

2026-05-04 00:52:42 -04:00

tsconfig.json

initial commit

2026-04-04 22:13:55 -04:00