refactor: add .dockerignore and update Dockerfile for improved build …

[SharanRP]

fix

Summary by CodeRabbit

• Chores
  • Improved Docker build efficiency and reduced image size by refining files and directories excluded from Docker builds.
  • Updated Docker build process for better caching and faster dependency management.
  • Adjusted release packaging to include only essential documentation files in archives.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces a new .dockerignore file to exclude unnecessary files from Docker build contexts, refines the .goreleaser.yml to limit documentation included in release archives, and optimizes the Dockerfile by separating dependency installation from source code copying to improve Docker layer caching efficiency.

Changes

Files / Grouped Files	Change Summary
.dockerignore	Added to exclude build artifacts, caches, test files, IDE/editor files, OS files, VCS files, and more.
.goreleaser.yml	Adjusted to only include docs/man/*.1 and docs/*.md in archives, narrowing documentation scope.
Dockerfile	Modified build stage to copy go.mod/go.sum before other sources, optimizing dependency caching.

Sequence Diagram(s)

sequenceDiagram
    participant Docker as Docker Engine
    participant FS as Project Filesystem

    Docker->FS: COPY go.mod, go.sum
    Docker->Docker: RUN go mod download
    Docker->FS: COPY rest of source files
    Docker->Docker: RUN go build ...

Loading

Possibly related PRs

• refactor: update Go base image to 1.22 and streamline Dockerfile inst… #3: Alters the Dockerfile by removing the separation of copying go.mod/go.sum and all source files, directly contrasting the caching optimization introduced here.

Poem

In Docker’s warren, files abound,
But now the clutter won’t be found!
With layers cached and docs refined,
The build hops forward, streamlined.
The rabbit cheers with gleeful might—
“Your Docker builds are feather-light!” 🐇🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a60f41 and d7518be.

📒 Files selected for processing (3)

• .dockerignore (1 hunks)
• .goreleaser.yml (1 hunks)
• Dockerfile (1 hunks)

---

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

CodeRabbit Configuration 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.