chore(justfile): beacon logs, restart rebuilding only sidecar

[thedevbirb]

Summary by CodeRabbit

• New Features
  • Introduced a new target for restarting the sidecar service, streamlining the development process.
  • Added a target to fetch and follow logs from the beacon node, enhancing debugging and monitoring capabilities.

[coderabbitai]

Walkthrough

The updates to the Justfile introduce two new targets that enhance the management of Docker containers in the development environment. The _restart-sidecar target simplifies the process of stopping, rebuilding, and starting the sidecar service, streamlining developer workflows. Additionally, the beacon-logs target allows users to easily access and follow logs from the beacon node associated with the cl-1-lighthouse-geth container, improving debugging and monitoring capabilities.

Changes

File	Changes Summary
Justfile	Added _restart-sidecar target for streamlined sidecar management. Added beacon-logs target for accessing logs of the beacon node in cl-1-lighthouse-geth container.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Justfile
    participant Docker

    Developer->>Justfile: Call _restart-sidecar
    Justfile->>Docker: @just down
    Justfile->>Docker: @just _build-sidecar
    Justfile->>Docker: @just up
    Developer->>Justfile: Call beacon-logs
    Justfile->>Docker: Retrieve logs from cl-1-lighthouse-geth
    Docker-->>Developer: Display beacon logs

Loading

---

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.
  • @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 as 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.

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

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 6f724a9 and 38c01ff.

Files selected for processing (1)

• Justfile (2 hunks)

Additional comments not posted (2)

Justfile (2)

30-33: LGTM!

The _restart-sidecar target correctly encapsulates the process of stopping, rebuilding, and starting the sidecar service.

---

60-62: LGTM!

The beacon-logs target correctly fetches and follows logs from the cl-1-lighthouse-geth container.