Use prisma db push instead of migrate deploy on startup
Eliminates the need to generate and commit migration files locally before first deploy. Schema is synced directly from schema.prisma on container start. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
15
README.md
15
README.md
@@ -48,20 +48,7 @@ PORT=3080
|
||||
|
||||
Point NPM at `http://<host-ip>:3080` for the proxy host.
|
||||
|
||||
### 3. Create the initial database migration
|
||||
|
||||
Run this **once** on your local dev machine before first deploy, then commit the result:
|
||||
|
||||
```bash
|
||||
cd server
|
||||
npm install
|
||||
# point at your local postgres or use DATABASE_URL from .env
|
||||
npm run db:migrate # creates prisma/migrations/
|
||||
```
|
||||
|
||||
Commit the generated `server/prisma/migrations/` folder — `prisma migrate deploy` in the container will apply it on startup.
|
||||
|
||||
### 4. Deploy
|
||||
### 3. Deploy
|
||||
|
||||
```bash
|
||||
docker compose pull
|
||||
|
||||
Reference in New Issue
Block a user