prisma generate needs over three minutes on the production host, which made
every deploy hang on that build step. The client is now generated on the dev
machine into prisma-client.tar.gz (tracked, 8.5MB) and the image just untars
it. Dropping the unused linux-musl engine target halves that payload.
Co-authored-by: Cursor <cursoragent@cursor.com>
Deploy is back to the flow that worked: build dist locally, push, then on the
server only `git pull` + `docker compose up -d --build`. The Dockerfile now
also takes prisma/ and package.json from git and runs `prisma generate`, so
schema and migration changes ship without rebuilding the 120MB node_modules
bundle. Removes the prebuilt compose path, which could never work on a server
without npm.
Co-authored-by: Cursor <cursoragent@cursor.com>
Dockerfile.prebuilt needs package.json, prisma, and node_modules in the build context; the previous ignore whitelist blocked them.
Co-authored-by: Cursor <cursoragent@cursor.com>
Allow Nest prefix server/api and overlay dist from git onto the deploy bundle so proxy paths match without a full retar.
Co-authored-by: Cursor <cursoragent@cursor.com>
Alpine musl is incompatible with host-built Prisma engines; use bookworm-slim and allow updating entrypoint without repacking the bundle.
Co-authored-by: Cursor <cursoragent@cursor.com>
Build on the developer machine without Docker, commit dist/, and run on the server with Dockerfile.dist plus compose env_file.
Co-authored-by: Cursor <cursoragent@cursor.com>
Install and build on the server host with npmmirror, then package a slim image without network during docker build.
Co-authored-by: Cursor <cursoragent@cursor.com>
Provide backend for admin and user apps with Postgres, migrations, seed data, and docker-compose for LiteSpeed reverse-proxy deployment.
Co-authored-by: Cursor <cursoragent@cursor.com>
mohmdsdgandCursor