Sensitive secrets and credentials committed to the repository

[way2nafea]

Description

Sensitive credentials appear to be committed to the repository.

Affected Files

• .env
• docker-compose.yml

Issue

The .env file appears to contain sensitive information such as application secret keys and database credentials. Additionally, docker-compose.yml includes database credentials.

Storing secrets directly in the repository increases the risk of accidental exposure and unauthorized access.

Expected Behavior

Sensitive credentials should not be committed to version control. Instead:

• Remove secrets from the repository.
• Add .env to .gitignore.
• Provide a .env.example file containing placeholder values.
• Use environment variables or a secure secret management solution for deployment.

Impact

• Potential credential leakage
• Unauthorized database access
• Increased security risk for deployments

I'd be happy to work on this issue if it's considered valid.

[github-actions]

👋 Welcome to DevLink!

Thank you for opening your first issue and contributing to our community.

Before getting started, please:

• Read the CONTRIBUTING guidelines.
• Search existing issues to avoid duplicates.
• Provide clear steps, screenshots, or feature details when applicable.

We appreciate your contribution and look forward to building DevLink together.

Happy coding! 🚀

[way2nafea]

Hi @nensii21,

I've opened this issue after noticing that sensitive credentials appear to be present in the repository. If the issue is valid, I'd be happy to work on resolving it.

Could you please assign it to me?

Thank you!

[way2nafea]

Hi @nensii21,

I've completed the implementation and submitted a Pull Request addressing this issue.

PR: #186

Kindly review it when you have time. Thank you!