feat: Add Docker Compose setup and update dependencies #101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit introduces a Docker Compose configuration to streamline the setup and development process for the frontend and backend services. Key changes: - Added `backend/Dockerfile` to containerize the backend Node.js application. - Added `frontend/Dockerfile` to containerize the frontend Next.js application. - Created `docker-compose.yml` in the root directory to define and orchestrate the frontend and backend services, configured for development with hot-reloading. - Updated dependencies in `package.json` files for root, frontend, and backend to their latest versions. This included addressing build issues in the frontend arising from major version upgrades (e.g., React 19, Tailwind CSS v4). - Updated `README.md` to remove old manual installation instructions and added a new section detailing how to set up and run the project using Docker Compose. The new setup aims to provide a consistent and reproducible environment for developers. Due to limitations in my current environment, I couldn't complete a full `docker-compose up` test, but I verified individual components (frontend build, backend syntax check, Dockerfile creation).
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds Docker-based setup for frontend and backend services and updates various project dependencies to streamline development and ensure consistency.
- Introduces Dockerfiles and a Docker Compose configuration for both services.
- Bumps dependency versions across root, frontend, and backend package.json files.
- Updates README with new Docker Compose setup instructions.
Reviewed Changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Bump root concurrently and knip devDependencies |
| frontend/tsconfig.json | Expanded "lib" array formatting and added "target" setting |
| frontend/src/components/ui/input-otp.tsx | Added inline typing for OTP context with an any cast |
| frontend/src/components/ui/button.tsx | Forwarded children and replaced rest-prop spread |
| frontend/src/components/theme-provider.tsx | Consolidated next-themes imports into one line |
| frontend/postcss.config.mjs | Updated PostCSS plugin key to @tailwindcss/postcss |
| frontend/package.json | Bumped numerous frontend dependencies and devDependencies |
| frontend/Dockerfile | Added Dockerfile for building and running the Next.js app |
| docker-compose.yml | Created Docker Compose config to orchestrate frontend/backend |
| backend/package.json | Bumped backend dependencies and devDependencies |
| backend/Dockerfile | Added Dockerfile for building and running the Node.js backend |
| README.md | Replaced manual install instructions with Docker Compose guide |
| ) | ||
| {...rest} | ||
| > | ||
| {children as any} |
There was a problem hiding this comment.
[nitpick] Casting children to any reduces type safety; update ButtonProps to include children?: React.ReactNode (if not already) and remove the as any cast.
Suggested change
| {children as any} | |
| {children} |
Copilot uses AI. Check for mistakes.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a Docker Compose configuration to streamline the setup and development process for the frontend and backend services.
Key changes:
backend/Dockerfileto containerize the backend Node.js application.frontend/Dockerfileto containerize the frontend Next.js application.docker-compose.ymlin the root directory to define and orchestrate the frontend and backend services, configured for development with hot-reloading.package.jsonfiles for root, frontend, and backend to their latest versions. This included addressing build issues in the frontend arising from major version upgrades (e.g., React 19, Tailwind CSS v4).README.mdto remove old manual installation instructions and added a new section detailing how to set up and run the project using Docker Compose.The new setup aims to provide a consistent and reproducible environment for developers. Due to limitations in my current environment, I couldn't complete a full
docker-compose uptest, but I verified individual components (frontend build, backend syntax check, Dockerfile creation).