chore: add Dockerfile and .dockerignore for containerization

[huamanraj]

fix: #20

Summary by CodeRabbit

• Chores
  • Updated Docker build configuration for improved efficiency and image optimization.
  • Implemented a multi-stage container build to streamline dependency installation and artifact generation.
  • Enhanced deployment security by running the application container with non-root user privileges.
  • Added image build exclusion rules to reduce unnecessary files included during Docker image creation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@huamanraj is attempting to deploy a commit to the Ketan's Personal Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Adds Docker support: a multi-stage Dockerfile for building and running a Next.js app, and a .dockerignore listing common artifacts to exclude from Docker build contexts (node_modules, build outputs, VCS files, logs, env files).

Changes

Cohort / File(s)	Summary
Docker configuration Dockerfile	Adds a multi-stage Dockerfile with deps, builder, and runner stages; installs dependencies depending on detected lockfile, builds Next.js, copies runtime artifacts, creates a non-root nextjs user, exposes port 3000, and sets start command.
Docker ignore rules .dockerignore	Introduces ignore rules to exclude common artifacts: node_modules, Next.js build output (e.g., .next), VCS files (.git, .gitignore), Dockerfiles, debug logs (npm-debug.log, yarn-error.log, pnpm-debug.log), and environment files (.env, .env.*).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Review artifact copy paths between stages (.next, node_modules, public, Prisma files).
• Verify package-manager detection and that fallback flows don't run redundant installs.
• Check for missing runtime dependencies (openssl/libc) and correct inclusion.
• Confirm non-root user creation and file ownerships permit runtime access.

Poem

🐰 I hopped in with a Docker song,
Three stages hummed and moved along.
Build then run with cautious cheer,
Ignore the crumbs, keep image clear.
🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is incomplete, containing only a single line 'fix: #20' without following the required template structure.	Complete the pull request description using the template: provide a Summary section explaining the changes, a Testing section describing how the changes were tested, and verify all checklist items are addressed.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: add Dockerfile and .dockerignore for containerization' clearly and specifically describes the main changes in the pull request.
Linked Issues check	✅ Passed	The changes successfully address the main objective of issue #20 by introducing Docker support through Dockerfile and .dockerignore files, enabling quick project setup for contributors.
Out of Scope Changes check	✅ Passed	All changes are directly related to Docker support requested in issue #20; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ceb646a and d779ce8.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Dockerfile

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ketankauntia]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1c97caa and ceb646a.

📒 Files selected for processing (2)

• .dockerignore (1 hunks)
• Dockerfile (1 hunks)

🧰 Additional context used

🪛 Hadolint (2.14.0)

Dockerfile

[error] 45-45: COPY with more than 2 arguments requires the last argument to end with /

(DL3021)

🔇 Additional comments (7)

.dockerignore (1)

1-12: LGTM! Solid exclusion patterns for Next.js.

The .dockerignore file covers the essential patterns: build artifacts, dependencies, version control files, logs, and environment variables. This will keep the Docker build context lean and prevent sensitive data leakage.

Dockerfile (6)

1-18: Well-structured dependency installation stage.

The conditional logic correctly handles npm, pnpm, and yarn with appropriate frozen-lockfile flags. Using corepack enable for pnpm is the right approach for Node.js 20.

---

20-31: Build stage looks good.

Copying dependencies from the deps stage and disabling telemetry are appropriate choices. The build process follows Next.js conventions.

---

33-41: Excellent security posture with non-root user.

Running as a non-root user (nextjs) is a security best practice. The production environment variables are correctly set.

---

57-61: Runtime configuration is correct.

The container properly runs as a non-root user, exposes the standard Next.js port, and uses the appropriate start command.

---

54-55: Prisma is a required dependency in this project (@prisma/client and prisma are both in dependencies/devDependencies, and the prisma/schema.prisma file exists). The COPY statement is correct and necessary—this is not optional and will not fail the build.

Likely an incorrect or invalid review comment.

---

51-52: No changes needed. Your Next.js configuration does not use output: 'standalone', so the Dockerfile correctly includes node_modules. The existing comment on line 51 accurately reflects this requirement.

Likely an incorrect or invalid review comment.