-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat: db changed to postgres #619
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
2074360 | Triggered | Generic Password | 3663a10 | browser-extension/docker-compose.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
Oh, nice! i was hoping the changes to be this minimal. |
}, | ||
test: { | ||
username: "root", | ||
password: null, | ||
database: "uli_test", | ||
host: "127.0.0.1", | ||
dialect: "mysql", | ||
dialect: "postgres", | ||
}, | ||
production: { | ||
username: process.env.DB_USERNAME, | ||
password: process.env.DB_PASSWORD, | ||
database: "uli_prod_unicode", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be picked up from the env too? process.env.DB_NAME
perhaps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eternaltyro hi, we have made that small change here - #620
is this the change you wanted?
This PR resolves issue #613.
Changes:
Other Changes in the
docker-compose
file:node_modules
folder. Previously, thenpm install
command in the API_Server Dockerfile required dependencies to be installed locally. This change ensures dependencies are available without needing local installation.docker compose up
command. By commenting out the linecommand: tail -f /dev/null
, everything worked smoothly. This line is still commented out as it may have been causing issues by overriding the default startup command.