[Feature] Add Docker support and publish container on Docker Hub

[mehradrafigh]

Problem

Right now, I have to pull the repository, npm install, npx prisma generate, npx prisma migrate dev --name init and npx next dev

Proposed solution

It would be more easier if there would be a docker-compose.yml available to run this all of this with containers. Additionally the application container could be built as part of the CI and pushed to Docker Hub

Alternatives considered

Alternative is to pull the repository, npm install, ....

Additional context

Nope, but I am happy to help with the Dockerfile, docker-compose.yml etc

[xiaoyao9184]

There is already a published image in #19, but the current Dockerfile still has several issues:

• prisma is in devDependencies but is not installed in the production image, which leads to missing Prisma CLI at runtime.
  

  Siftly/docker/Dockerfile

  Lines 28 to 31 in 61e7bde

  	RUN npm ci --omit=dev
  	# Re-generate Prisma client in runner stage
  	RUN node_modules/.bin/prisma generate

• better-sqlite3 does not need to be built from source. npm ci will not build it from source in this case, so that step is unnecessary.
  

  Siftly/docker/Dockerfile

  Lines 5 to 6 in 61e7bde

  	# Native module build deps (required by better-sqlite3)
  	RUN apk add --no-cache python3 make g++

• this is a very dangerous operation:
  

  Siftly/docker/Dockerfile

  Line 15 in 61e7bde

  COPY . .

  It may copy existing node_modules from the host into the image.

  I tried to fix the missing Prisma CLI by using:

  COPY --from=builder /app/node_modules ./node_modules

  but this caused environment pollution.

  A better approach is to add a .dockerignore file to exclude node_modules. This will also speed up the build process.

---

Here is a complete working example of a Dockerfile:

dockerfile

# ── builder ───────────────────────────────────────────────────────────────────
FROM node:22-alpine AS builder
WORKDIR /app

COPY package*.json ./
COPY prisma ./prisma
RUN npm ci

# Generate Prisma client
RUN node_modules/.bin/prisma generate

COPY . .
RUN npm run build

# ── runner ────────────────────────────────────────────────────────────────────
FROM node:22-alpine
WORKDIR /app

RUN addgroup -S appgroup && adduser -S appuser -G appgroup

# Install production deps (includes prisma + better-sqlite3, rebuilt for this image)
COPY package*.json ./
COPY prisma ./prisma
RUN npm ci --omit=dev

# Re-generate Prisma client in runner stage
RUN npm install prisma@$(node -p "require('./package.json').devDependencies.prisma") --no-save
RUN node_modules/.bin/prisma generate

# Copy built Next.js output
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/public ./public
COPY --from=builder /app/next.config.ts ./next.config.ts
COPY --from=builder /app/prisma.config.ts ./prisma.config.ts

# Entrypoint
COPY docker/docker-entrypoint.sh ./docker-entrypoint.sh
RUN chmod +x ./docker-entrypoint.sh

RUN mkdir -p /data && chown -R appuser:appgroup /app /data
USER appuser

EXPOSE 3000

# /data is the volume mount point for the SQLite database
VOLUME ["/data"]

CMD ["./docker-entrypoint.sh"]

.dockerignore

.git
.github
.next
app/generated
docker/*
!docker/docker-entrypoint.sh
node_modules
.dockerignore
.env
.env.example
.gitignore
*.log
*.db

---

Finally, prisma still needs to be moved from devDependencies to dependencies.