Skip to content
This repository was archived by the owner on May 30, 2025. It is now read-only.

docs: add deploy steps to readme#29

Merged
gupadhyaya merged 1 commit intomainfrom
tzdybal/readme_deploy
Feb 18, 2025
Merged

docs: add deploy steps to readme#29
gupadhyaya merged 1 commit intomainfrom
tzdybal/readme_deploy

Conversation

@tzdybal
Copy link
Contributor

@tzdybal tzdybal commented Feb 18, 2025

Overview

Steps to test deployment added to readme.

Summary by CodeRabbit

  • Documentation
    • Updated setup instructions to include new commands for executing the middleware binary with JWT configuration.
    • Added detailed, step-by-step guidance for compiling and starting the rollkit application from a specific branch.

@coderabbitai
Copy link

coderabbitai bot commented Feb 18, 2025

Walkthrough

This pull request updates the README.md file by adding new instructions. The additions include details on executing the evm-middleware binary with a JWT secret and steps for checking out the feature/exec_api branch, building the rollkit, and starting it. There are no deletions or modifications to existing instructions.

Changes

File Change Summary
README.md Added new instructions for running the evm-middleware binary with a JWT secret and for compiling and starting rollkit from the feature/exec_api branch.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant EM as EVM-Middleware
    participant RK as Rollkit
    Dev->>EM: Run "evm-middleware" with JWT secret
    EM-->>Dev: Middleware started
    Dev->>Dev: Checkout branch `feature/exec_api`
    Dev->>RK: Build and start Rollkit
    RK-->>Dev: Rollkit running
Loading

Possibly related PRs

  • feat: minimal binary #11: Introduced a minimal binary implementation for the evm-middleware, which relates directly to the updated instructions for executing the binary and compiling rollkit.

Poem

I'm a rabbit with a twitch and a hop,
Coding new paths that just won't stop.
README updated with fresh command cheer,
EVM and Rollkit are finally here!
Hop along to run the code, dear friend,
With every line, magic we blend.
🐇✨


📜 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 37020bf and 365d926.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • README.md

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
🪧 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.
    • 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@RollkitBot RollkitBot requested a review from a team February 18, 2025 16:18
@RollkitBot RollkitBot requested review from Manav-Aggarwal, tuxcanfly and yarikbratashchuk and removed request for a team February 18, 2025 16:18
@tzdybal tzdybal force-pushed the tzdybal/readme_deploy branch from 37020bf to 365d926 Compare February 18, 2025 16:21
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
README.md (3)

78-83: Enhance Markdown Fence Formatting for evm-middleware Instructions

The new instructions for running the evm-middleware binary are clear and add value to the deployment documentation. However, to satisfy markdown lint guidelines (MD031), please ensure that fenced code blocks are surrounded by blank lines. For example, insert a blank line before and after the ```bash code fence.

-78~
-Run `evm-middleware` binary:
-79~
-```bash
-./build/evm-middleware run --jwt-secret $(cat docker/jwttoken/jwt.hex)
-```
-82~
+78~
+Run `evm-middleware` binary:
+79~
+
+```bash
+./build/evm-middleware run --jwt-secret $(cat docker/jwttoken/jwt.hex)
+```
+82~
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

80-80: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

🪛 GitHub Actions: CI and Release

[warning] 80-80: MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines [Context: "```bash"]


84-90: Improve Markdown Fence Spacing for Rollkit Deployment Instructions

The additional instructions for compiling and running rollkit from the feature/exec_api branch are well detailed. To adhere to markdown guidelines (MD031), please add blank lines before and after the fenced code block. This enhancement improves readability and reduces markdown lint warnings.

-84~
-Compile rollkit from `feature/exec_api` branch and run it:
-85~
-```bash
-git checkout feature/exec_api
-go build ./cmd/rollkit
-./rollkit start
-```
-90~
+84~
+Compile rollkit from `feature/exec_api` branch and run it:
+85~
+
+```bash
+git checkout feature/exec_api
+go build ./cmd/rollkit
+./rollkit start
+```
+90~
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

85-85: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

🪛 GitHub Actions: CI and Release

[warning] 85-85: MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines [Context: "```bash"]


91-91: Eliminate Excessive Blank Lines

There appear to be multiple consecutive blank lines at the end of the file (MD012). Please reduce them to a single blank line to comply with markdown best practices.

-91
-
-
+91
+
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

91-91: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

🪛 GitHub Actions: CI and Release

[warning] 91-91: MD012/no-multiple-blanks: Multiple consecutive blank lines [Expected: 1; Actual: 2]

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e35a748 and 37020bf.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

80-80: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)


85-85: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

🪛 GitHub Actions: CI and Release
README.md

[warning] 80-80: MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines [Context: "```bash"]


[warning] 85-85: MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines [Context: "```bash"]


[warning] 91-91: MD012/no-multiple-blanks: Multiple consecutive blank lines [Expected: 1; Actual: 2]

@tzdybal tzdybal requested a review from gupadhyaya February 18, 2025 16:21
@gupadhyaya gupadhyaya added this pull request to the merge queue Feb 18, 2025
Merged via the queue into main with commit 1d12dc9 Feb 18, 2025
10 checks passed
@tac0turtle tac0turtle removed this from Evolve Apr 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants