fix(docker): run database migrations before server starts

This ensures migrations are applied before Next.js app preparation,
preventing "column does not exist" errors when new columns are added
to the schema.

Changes:
- Add migration.ts as esbuild entry point (compiles to dist/migration.mjs)
- Update Dockerfile CMD to run migrations before server start
- Update Dockerfile.cloud with same migration approach

The proper startup order is now:
1. Run dist/migration.mjs (applies pending migrations)
2. Run pnpm start (starts the server)

This is the standard pattern for production deployments where database
schema must be updated before the application starts making queries.

Author: claude

Dockerfile

@@ -65,4 +65,5 @@ RUN curl -sSL https://railpack.com/install.sh | bash
 COPY --from=buildpacksio/pack:0.35.0 /usr/local/bin/pack /usr/local/bin/pack
 
 EXPOSE 3000
-CMD [ "pnpm", "start" ]
+# Run database migrations before starting the server
+CMD node -r dotenv/config dist/migration.mjs && pnpm start

Dockerfile.cloud

@@ -60,4 +60,5 @@ RUN curl https://rclone.org/install.sh | bash
 RUN pnpm install -g tsx
 
 EXPOSE 3000
-CMD [ "pnpm", "start" ]
+# Run database migrations before starting the server
+CMD node -r dotenv/config dist/migration.mjs && pnpm start

apps/dokploy/esbuild.config.ts

@@ -24,6 +24,7 @@ try {
 		.build({
 			entryPoints: {
 				server: "server/server.ts",
+				migration: "migration.ts",
 				"reset-password": "reset-password.ts",
 				"reset-2fa": "reset-2fa.ts",
 			},