Updating the setup script to handle sample data import for Docker

[Suyash878]

What kind of change does this PR introduce?

Bug Fix

Issue Number:

Fixes #2270

Did you add tests for your changes?

No

Snapshots/Videos:

If relevant, did you update the documentation?

Not sure

Summary

The setup script will now prompt the user when it starts the process for sample data import provided the user is using Docker.

Does this PR introduce a breaking change?

No

Other information

This PR was supposed to be made against the develop-postgres branch but since it is currently under work, and unavailability of the setup script there I am currently raising the PR against the develop branch. My changes may get introduced to the develop-postgres branch as a seperate issue later on.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features

  • Introduced a new shell script (entrypoint.sh) for importing sample data.
  • Enhanced Docker setup process to automatically create and execute the entrypoint.sh script for importing sample data, with improved error handling.

• Bug Fixes

  • Ensured existing MongoDB and Redis configurations remain unaffected during the setup process.

[coderabbitai[bot]]

Walkthrough

A new shell script file entrypoint.sh has been added to facilitate the importation of sample data into the application. This script is created and executed within the setup.ts file when the setup process detects a Docker environment. The integration of this functionality enhances the setup process for Docker installations, ensuring that sample data can be imported automatically.

Changes

File	Change Summary
entrypoint.sh	New file created to execute npm run import:sample-data.
setup.ts	Enhanced setup process for Docker; added logic to create and execute entrypoint.sh for data import.

Assessment against linked issues

Objective	Addressed	Explanation
Prompt user for data import if Docker is running and store previous answers (#2270)	❌	The script does not prompt for data import.
Ensure sample data is imported correctly in Docker setup (#2270)	✅
Provide error handling for non-Docker data import (#2270)	❌	No error handling for non-Docker scenarios.

Possibly related PRs

• 2512: The changes in setup.ts related to the creation and execution of the entrypoint.sh script for importing sample data directly connect to the main PR, which introduces this script.

Suggested reviewers

• DMills27

Poem

In the land of code where rabbits play,
A script was born to save the day.
With entrypoint.sh, data flows,
In Docker's arms, our project grows.
Hop along, dear coder, with glee,
Sample data's here, as easy as can be! 🐇✨

---

📜 Recent review details

**Configuration used: .coderabbit.yaml** **Review profile: CHILL**

📥 Commits

Reviewing files that changed from the base of the PR and between 6144664a70cd2e1b5da805d72eed3703b1c5879d and 0146c7f8af12a3e6f2d509d3d537d0ab16831441.

📒 Files selected for processing (1)

* `setup.ts` (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

* setup.ts

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[github-actions[bot]]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them. When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. :dart: Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[varshith257]

@Suyash878 Isn't sample data is imported into docker mango container?

[Suyash878]

Yes, sample data would be imported to the docker mongo container, totally depends on the mongodb url in the environment variables.

[palisadoes]

Please fix the failing tests