Skip to content

feat: add Prisma schema and automated migrations - #7

Merged
theNEXlevel merged 2 commits into
mainfrom
feat/prisma-migrations
Sep 13, 2026
Merged

theNEXlevel merged 2 commits into
mainfrom
feat/prisma-migrations

Conversation

@theNEXlevel

Copy link
Copy Markdown
Contributor

Summary

  • Add the introspected MySQL Prisma schema, split into model and enum files with a shared YesNo enum.
  • Add Prisma 7 configuration and the 0_init baseline migration.
  • Apply pending migrations during container startup with connection retries.
  • Add disposable MySQL migration coverage to CI and publish smoke tests.
  • Package Prisma and dotenv correctly in the production image.

Verification

  • Built and started the local Docker Compose stack with a disposable MySQL database.
  • Confirmed 0_init applied successfully and 20 tables were created.
  • Confirmed /api/health returned status ok and the app container became healthy.

Deployment note

Before the first automatic migration deploy against an existing production database, mark the baseline migration as applied with prisma migrate resolve --applied 0_init.

@theNEXlevel
theNEXlevel merged commit b991bad into main Sep 13, 2026
1 check passed
@theNEXlevel
theNEXlevel deleted the feat/prisma-migrations branch September 13, 2026 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant