Open
Conversation
Owner
There was a problem hiding this comment.
For review purposes it's fine, but we should never push the changes with a .env file. The reason is that, this .env is environment specific. On our PC there might be a MySQL server running locally with a different username and password.
Similarly, Another team member may spin up a container and point to a MySQL server running on cloud.
| @@ -0,0 +1,19 @@ | |||
| FROM maven:3.8.1-openjdk-17 AS build | |||
Owner
There was a problem hiding this comment.
Is this "build" alias supposed to be used anywhere ?
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
2 participants
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.
To build the image, a Dockerfile was created with maven:3.8.1-openjdk-17 as a base image. A docker compose file was created with two services(containers): mysql, which runs a mysql instance, and userapp, which is built using the Dockerfile and runs the Java application. The environment variables for both containers are stored in '.env' and referenced in the docker compose. Both containers are configured to be part of the same internal network to ensure successful communication between the applications.