Seeding script

[VJagiasi]

Notion ticket link

Create Seeding Script

Implementation description

• Added the seeding script using snaplet to implement seeding and used faker to generate date
• Added the seeding script running, sync and migration database commands to package.json

Steps to test

It will automatically seed when you run docker compose up --build

Steps to test manually*

1. Ensure the database is running locally and make sure you have initialized the database npx prisma migrate dev --name init
2. In the root directory, npx @snaplet/seed sync to sync the seed file to any change in the data models of the database
3. npx prisma db seed to seed the database based on seed.ts
4. Run docker exec -it sistema-db-1 /bin/bash and then in the container run psql -U sistema -d sistema to enter the Postgres shell
5. In the Postgres shell check if the database tables are seeded by running SELECT * FROM public."<Table-name>"; eg: SELECT * FROM public."Absence";

What should reviewers focus on?

• All the tables are seeded correctly with correct data and are in sync with each other

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[ChinemeremChigbo]

Please also add instructions for running the seeding script to the README.

[VJagiasi]

Please also add instructions for running the seeding script to the README.

Added

[ChinemeremChigbo]

Please fix your merge conflicts and make sure your seeding script matches the updated schema.

[ChinemeremChigbo]

Conditional-Postinstall seems to be required for the seeding script to not interfere with deployment. I tried removing it and reverting to only using start.sh, but the deployments failed after that occurred, which is likely due to Prisma needing different Postinstall scripts to work locally and in deployment. Error messages could not be viewed due to a lack of Vercel pro accounts.

Fixed the failing builds. We need to sync @ludavidca @anantduggal @RahulTandon1 to fix the lack of build introspection.

[ludavidca]

Looks good to me. All issues are resolved.

[ChinemeremChigbo]

LBTM