refactor: add db seed command in docker files
What
Refactored the Docker configuration to include the database seed command. This ensures that the database is seeded during the container initialization process, automating the setup required for local development and testing environments.
Why
Seeding the database manually can be error-prone and time-consuming. Automating this step as part of the Docker process improves consistency, reduces human error, and simplifies onboarding for new developers.
How
- Updated Dockerfile to include the database seed command.
- Modified the Dockerfiles to ensure the seed step is executed as part of the container startup.
- Ensured that the seeding process works seamlessly with ts-node and Prisma by using the existing execPromise logic to handle any errors or output.
Quality Gate failed
Failed conditions
15 Security Hotspots
B Maintainability Rating on New Code (required ≥ A)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension
SonarLint
Quality Gate failed
Failed conditions
15 Security Hotspots
B Maintainability Rating on New Code (required ≥ A)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension
SonarLint
@KambleSahil3 I think we can close this PR. Can you please confirm?
@GHkrishna Yes, this PR can be closed
Closing as not required