Conversation
… database configuration
…ervices to docker-compose files
… and command usage
Dockerize
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
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 pull request introduces a new CI/CD workflow for automated deployment to EC2, refactors the Docker build process to use a multi-stage build for better performance and security, and updates Docker Compose configurations for both development and production environments. Additionally, it makes minor codebase improvements and environment standardization.
CI/CD and Deployment Automation:
.github/workflows/deploy.yaml) that builds the Docker image, pushes it to Docker Hub, and deploys the application to an EC2 instance using SSH and Docker Compose.Docker and Docker Compose Improvements:
Dockerfileto use a multi-stage build (builder and runtime stages), upgrades to Node.js 22-alpine, and optimizes dependency installation and build steps for production.docker-compose.prod.yamlto use the latest Docker image from Docker Hub for the backend service, standardizing environment variables and networking.docker-compose.override.yamlfor local development, allowing the backend to be built from source with live reloading and development-friendly settings.docker-compose.yaml, centralizing environment-specific configuration in override and production files.Minor Codebase Improvements:
PrismaClientinlib/prisma.tsto use the standard@prisma/clientpackage.src/main.tsfrom 5500 to 5000 for consistency with Docker and Compose configurations.