Docker: Add .dockerignore to setup clean workspace for docker build

[glensc]

This improves local rebuilds cache if unrelated files are changed.

For example modifying entrypoint.sh does not invalidate rebuild of java sources.

[coderabbitai]

Walkthrough

This update introduces a .dockerignore file, which is configured to exclude all files from the Docker context except for a select few essentials. Specifically, it keeps build.sbt, docker/entrypoint.sh, the project directory, and the src directory. This change streamlines the Docker build process by minimizing the build context, potentially improving build performance and reducing the size of the build.

Changes

Files	Change Summary
.dockerignore	Added; ignores all except build.sbt, docker/entrypoint.sh, project/*, src/*

🐇✨
A Docker tale, fresh and new,
With files so few, the build flew.
build.sbt, entrypoint.sh, in the crew,
Alongside project, src, a selective view.
Through the .dockerignore, we pursue,
A streamlined build, as our code stew.
🚀🌟

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
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 9b31fad and 4237e6c.

Files selected for processing (1)

• .dockerignore (1 hunks)

Additional comments not posted (1)

.dockerignore (1)

1-6: The .dockerignore file is well-configured to optimize Docker builds by excluding unnecessary files, aligning with the PR objectives. Ensure all necessary files and directories are included for a successful build.

[nylonee]

Good thinking!