Skip to content
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

Added environment variable for max connection #46

Closed
wants to merge 20 commits into from
Closed

Added environment variable for max connection #46

wants to merge 20 commits into from

Conversation

AtulRajput01
Copy link

**Added environment variable for max connection **

This PR addresses issue #18 add a new environment variable, PG_MAX_CONNECTIONS, to the docker-compose.yml file in order to configure the maximum number of database connections for the TimescaleDB service. By setting the value to 10, we can increase the maximum allowed connections to improve scalability and accommodate higher traffic.

@gitguardian
Copy link

gitguardian bot commented Jun 4, 2023

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
- AWS Keys 7b406dc Dockerfile View secret
- AWS Keys da00cfc docker-compose.yml View secret
- AWS Keys a76b405 bitnami/Dockerfile View secret
- AWS Keys 1d08705 Dockerfile View secret
- AWS Keys 706f7e9 bitnami/Dockerfile View secret
- AWS Keys f18770e docker-compose.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@AtulRajput01 AtulRajput01 closed this by deleting the head repository Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant