Add PEPTIDE_RPC variable check and endpoint in entrypoint.sh

[Inkvi]

Summary by CodeRabbit

• New Features

  • Added support for a new environment variable, PEPTIDE_RPC, ensuring better configuration management.

• Bug Fixes

  • Updated error messages to include guidance for setting the new PEPTIDE_RPC variable, improving user feedback.

[coderabbitai]

Walkthrough

The changes to the entrypoint.sh script enhance its functionality by adding a check for the new environment variable PEPTIDE_RPC. This ensures that all required variables must be set before execution. The error message has been updated to include this new variable, and the script now integrates PEPTIDE_RPC into the command that runs the cached Ethereum RPC, improving its operational requirements and clarity for users.

Changes

Files	Change Summary
entrypoint.sh	Added check for PEPTIDE_RPC alongside existing variables. Updated error messages and command usage to include PEPTIDE_RPC.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EntryPoint
    participant EthereumRPC

    User->>EntryPoint: Execute script
    EntryPoint->>EntryPoint: Check required env variables
    EntryPoint->>User: Error if any variable missing
    EntryPoint->>EthereumRPC: Execute with configured endpoints

Loading

Poem

🐇 In the script where variables play,
A new friend joins, hip-hip-hooray!
PEPTIDE_RPC hops in line,
Ensuring all is set just fine.
With checks in place, we’re good to go,
Off to the blockchain, let the data flow! 🌟

---

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: CHILL

Commits

Files that changed from the base of the PR and between 25a99b9 and e26dc24.

Files selected for processing (1)

• entrypoint.sh (2 hunks)

Additional comments not posted (2)

entrypoint.sh (2)

7-9: Environment variable check is well-implemented.

The inclusion of PEPTIDE_RPC in the environment variable check ensures that all necessary variables are set, preventing potential runtime errors.

---

18-18: Integration of PEPTIDE_RPC into the command is correct.

The addition of --endpoint=peptide="$PEPTIDE_RPC" ensures that the new environment variable is utilized in the command execution.

[dshiell]

lgtm