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

feat: db changed to postgres #619

Merged
merged 1 commit into from
Sep 16, 2024
Merged

Conversation

maanasb01
Copy link
Collaborator

This PR resolves issue #613.

Changes:

  • Replaced the Docker image of MySQL with the Postgres image.
  • Updated the API_Server codebase to work with Postgres instead of MySQL. The required changes were minor and primarily made in the config file.
  • I, along with @aatmanvaidya, tested the Postgres database locally. All basic CRUD operations and other relevant operations functioned as expected. Additionally, we regenerated the production database dump locally on the new Postgres database, and everything seemed to have worked properly.

Other Changes in the docker-compose file:

  • Added a line in the "volumes" section to persist the node_modules folder. Previously, the npm install command in the API_Server Dockerfile required dependencies to be installed locally. This change ensures dependencies are available without needing local installation.
  • I encountered errors when running the docker compose up command. By commenting out the line command: 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.

Copy link

gitguardian bot commented Sep 16, 2024

⚠️ GitGuardian has uncovered 1 secret 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
2074360 Triggered Generic Password 3663a10 browser-extension/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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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.

@dennyabrain
Copy link
Contributor

Oh, nice! i was hoping the changes to be this minimal.

@dennyabrain dennyabrain merged commit ba05b9e into tattle-made:main Sep 16, 2024
3 checks passed
},
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",

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?

Copy link
Collaborator

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?

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.

4 participants