-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Secure Docker Compose Configuration by Using .env File #79
Labels
Comments
hi @jayanth-kumar-morem can you assign this task to me I would like to contribute to this . |
Pull request #104: |
@jayanth-kumar-morem can u plz check my Pull request #104 and kindly merge it . |
@PiyushRaj927 to pick this.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, our Docker Compose configuration contains sensitive information such as the PostgreSQL username and password. This information is directly written in the docker-compose.yml file, which is not a secure practice and could lead to accidental exposure of these details.
To enhance the security of our setup, we should move these sensitive details to a separate
.env.sample
file. Docker Compose automatically reads from a.env.sample
file in the same directory as thedocker-compose.yml
file, if it exists.Tasks:
.env.sample
file in the same directory as thedocker-compose.yml
file.POSTGRES_USER
andPOSTGRES_PASSWORD
environment variables from thedocker-compose.yml
file to the.env.sample
file.docker-compose.yml
file to reference these variables from the.env.sample
file..env.sample
file with their specific details.Acceptance Criteria:
docker-compose.yml
file no longer contains thePOSTGRES_USER
andPOSTGRES_PASSWORD
environment variables directly..env.sample
file is created and contains thePOSTGRES_USER
andPOSTGRES_PASSWORD
environment variables.The text was updated successfully, but these errors were encountered: