-
Notifications
You must be signed in to change notification settings - Fork 302
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
docs: tutorial for running hardware node #4678
Conversation
72956f1
to
5ac1340
Compare
5ac1340
to
adda5b1
Compare
adda5b1
to
3bb54b3
Compare
117fa5e
to
c00ee9a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple potential comment cleanups
blocks streaming in. If not, see the [debugging steps](../node/pd/debugging.md) | ||
to figure out what went wrong. | ||
|
||
<!-- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
this guide demonstrates how a user can self-host an RPC URL for use by themselves and others. | ||
|
||
<!-- | ||
Plan: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
Documents the setup process for renting a hardware box (via Hetzner) and configuring a fullnode on it. Necessarily overlaps with the regular ol' install docs for pd, but tried to be explicit in the tutorial for maximum comprehension.
There's a lot of unused content in here, so I'm cleaning out a ton of cruft from the repo, mostly ci- and deployment-related.
c00ee9a
to
c9f0903
Compare
## Describe your changes Refs #4678. ## Issue ticket number and link ## Checklist before requesting a review - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > docs-only Co-authored-by: Conor Schaefer <conor@penumbralabs.xyz>
We'd previously been triggering container builds on every merge to main, via the testnet deploy workflows, which were removed in #4678. Let's add triggers to build containers regularly, even though we're not deploying them automatically. Also cleans up unused builds like for galileo and grafana.
## Describe your changes We'd previously been triggering container builds on every merge to main, via the testnet deploy workflows, which were removed in #4678. Let's add triggers to build containers regularly, even though we're not deploying them automatically. Also cleans up unused builds like for galileo and grafana. ## Issue ticket number and link N/A ## Checklist before requesting a review - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > ci-only, no code changes Co-authored-by: Conor Schaefer <conor@penumbralabs.xyz>
Describe your changes
Documents the setup process for renting a hardware box (via Hetzner) and configuring a fullnode on it. Necessarily overlaps with the regular ol' install docs for pd, but tried to be explicit in the tutorial for maximum comprehension.
Making that simplified change, I looked through the old deployment/ci configs and culled a lot that were gathering dust. Now the repo concisely recommends using the systemd config, or links out to other community-maintained options for configuring nodes.
Issue ticket number and link
None.
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: