Skip to content

feat: mention artela specific stuff when running full node and connecting m… #504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

yarikbratashchuk
Copy link
Contributor

@yarikbratashchuk yarikbratashchuk commented Nov 13, 2024

Summary by CodeRabbit

  • New Features

    • Updated documentation for setting up a full node in a Rollkit-based blockchain network.
    • Added Docker usage instructions for the Artela EVM++ setup.
  • Improvements

    • Enhanced clarity and readability of guides with specific commands and configuration details.
    • Included tips for resolving common issues during setup, particularly for EVM clients.
    • Expanded instructions for accessing testing accounts and building on EVM++.
  • Documentation

    • Retained essential instructions while refining existing content for better user guidance.
    • Removed outdated tutorial link from the navigation structure for improved user experience.
    • Added SVG definition for the Telegram icon in the site configuration.

Copy link
Contributor

coderabbitai bot commented Nov 13, 2024

Walkthrough

The changes involve updates to three documentation files: guides/full-node.md, tutorials/artela-evm-plus-plus.md, and .vitepress/config.ts. The full-node.md file now includes clearer instructions for setting up a full node in a Rollkit-based blockchain, with modifications to configuration paths and initialization commands. The artela-evm-plus-plus.md file provides enhanced clarity on using Docker, accessing testing accounts, and modifying runtime parameters, along with improved structure and readability. The .vitepress/config.ts file updates the sidebar configuration and adds a new SVG for the Telegram icon.

Changes

File Change Summary
guides/full-node.md Updated instructions for full node setup, changed config path, specified initialization command, added notes on P2P connection and EVM error handling.
tutorials/artela-evm-plus-plus.md Enhanced clarity on Docker usage, expanded access to testing accounts, refined configuration steps, and improved document structure.
.vitepress/config.ts Removed entry for "Omni Octane EVM" tutorial link, added SVG definition for Telegram icon.

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • gupadhyaya
  • jcstein
  • Manav-Aggarwal
  • tzdybal

🐇 In the land of code where changes bloom,
Full nodes now thrive, dispelling the gloom.
With Docker and paths all laid out clear,
Setting up nodes brings us all cheer!
So hop along, dear coder friends,
To Rollkit's embrace, where the fun never ends! 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9869526 and 454ad72.

📒 Files selected for processing (1)
  • .vitepress/config.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • .vitepress/config.ts

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

@yarikbratashchuk yarikbratashchuk changed the title Mention artela specific stuff when running full node and connecting m… feat: mention artela specific stuff when running full node and connecting m… Nov 13, 2024
Copy link
Contributor

github-actions bot commented Nov 13, 2024

PR Preview Action v1.4.8
🚀 Deployed preview to https://rollkit.github.io/docs-preview/./pr-504/
on branch main at 2024-11-26 13:46 UTC

Copy link
Contributor

@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: 1

🧹 Outside diff range and nitpick comments (3)
guides/full-node.md (1)

85-85: Fix grammatical and spelling issues in the tip section.

The tip provides valuable operational guidance, but there are some minor issues to address.

Apply this diff to fix the issues:

-If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferrably to run a full node on a different machine, as some EVM clients does not have a configurable data directory.
+If your rollup uses EVM as an execution layer, and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferably run a full node on a different machine, as some EVM clients do not have a configurable data directory.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)

tutorials/artela-evm-plus-plus.md (2)

Line range hint 24-27: Enhance Docker prerequisites section.

Consider adding more specific details about host network mode requirements and potential issues users might encounter.

Add a note explaining:

  • Why host network mode is required
  • Common issues and their solutions
  • Platform-specific requirements (Windows/Mac/Linux)
🧰 Tools
🪛 Markdownlint

106-106: null
Bare URL used

(MD034, no-bare-urls)


Line range hint 71-82: Add examples of common configuration changes.

The configuration section could be more helpful with examples of frequently modified parameters.

Consider adding:

  • Common runtime parameters that users might want to modify
  • Example configurations for different use cases
  • Best practices for configuration changes
🧰 Tools
🪛 Markdownlint

106-106: null
Bare URL used

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 908e95d and dc06dc0.

📒 Files selected for processing (2)
  • guides/full-node.md (1 hunks)
  • tutorials/artela-evm-plus-plus.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
guides/full-node.md

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)

yarikbratashchuk and others added 2 commits November 14, 2024 11:10
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 37de0e6 and 9a564fa.

📒 Files selected for processing (1)
  • .vitepress/config.ts (1 hunks)

Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (2)
guides/full-node.md (2)

85-85: Consider adding Docker configuration example.

Since Docker is recommended as a solution, it would be helpful to provide a basic Docker configuration example or link to Docker-specific setup instructions. This would make it easier for users to follow the recommended approach.

Would you like me to help draft a Docker configuration example section?

🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)


85-85: Fix grammatical and spelling issues.

Please correct the following issues in the tip section:

  • "layar" → "layer"
  • "Preferrably" → "Preferably"
  • Add a comma before "and" in the compound sentence

Here's the corrected text:

-If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferrably to run a full node on a different machine (or using Docker), as some EVM clients does not have a configurable data directory.
+If your rollup uses EVM as an execution layer, and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferably run a full node on a different machine (or using Docker), as some EVM clients do not have a configurable data directory.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9a564fa and 426a635.

📒 Files selected for processing (2)
  • .vitepress/config.ts (0 hunks)
  • guides/full-node.md (1 hunks)
💤 Files with no reviewable changes (1)
  • .vitepress/config.ts
🧰 Additional context used
🪛 LanguageTool
guides/full-node.md

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)

🔇 Additional comments (1)
guides/full-node.md (1)

Line range hint 15-19: LGTM! Good separation of data directories.

The change to use a distinct configuration directory for the full node (_fn suffix) helps prevent conflicts between the sequencer and full node data, which is a good practice.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ur rollup uses EVM as an execution layar and you see an error like `datadir already ...

(COMMA_COMPOUND_SENTENCE)

Copy link
Member

@jcstein jcstein left a comment

Choose a reason for hiding this comment

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

utACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants