Skip to content
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

Public documentation for running a Scroll node #166

Merged
merged 4 commits into from
Apr 2, 2024

Conversation

isabellewei
Copy link
Contributor

Description

guide on how to run a Scroll node

other changes

  • modified the Aside component so that it can display no title

Copy link

netlify bot commented Feb 8, 2024

Deploy Preview for scroll-documentation ready!

Name Link
🔨 Latest commit 1454a2f
🔍 Latest deploy log https://app.netlify.com/sites/scroll-documentation/deploys/65d7cb7aafbeaa00088988b9
😎 Deploy Preview https://deploy-preview-166.docs.scroll.xyz/en/developers/guides/running-a-scroll-node
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dghelm dghelm requested a review from Thegaram February 12, 2024 19:09
@dghelm
Copy link
Collaborator

dghelm commented Feb 12, 2024

As mentioned in conversation, I'd love to see an intro to this clarifying who the audience is, since this is a "guide" and not just a technical reference. Maybe mention that many developers will use the public RPC and then advance to managed infrastructure by RPC providers in the ecosystem. Also to make clear that this is a "follower node" that can participate in the public mempool of transactions, but does not participate in consensus or block building.

Lastly, can we have subheadings in troubleshooting that labels each error? It kind of runs together as it displays now.

1. Run the `l2geth` container using the name `l2geth-docker`:

```bash
$ docker run --rm --name l2geth-docker -v $(pwd):/volume -p 8545:8545 -e RUST_LOG="info" -e CHAIN_ID="534352" scrolltech/l2geth:latest \
Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, does it break without CHAIN_ID="534352"?

</ToggleElement>

---
## Troubleshooting
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the first two could be removed, they seem to be irrelevant now

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm just going to remove the entire Troubleshooting section then

@dghelm dghelm merged commit 39bb7e0 into develop Apr 2, 2024
6 checks passed
@isabellewei isabellewei deleted the isabellewei/running-a-node branch April 24, 2024 21:52
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