docs: tutorial for running hardware node #4678
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
conorsch
force-pushed
the
docs-node-tutorial
branch
from
72956f1
to
5ac1340
Compare
conorsch
changed the title
conorsch
force-pushed
the
docs-node-tutorial
branch
from
5ac1340
to
adda5b1
Compare
conorsch
force-pushed
the
docs-node-tutorial
branch
from
adda5b1
to
3bb54b3
Compare
conorsch
force-pushed
the
docs-node-tutorial
branch
from
117fa5e
to
c00ee9a
Compare
aubrika
approved these changes
Jun 28, 2024
| blocks streaming in. If not, see the [debugging steps](../node/pd/debugging.md) | ||
| to figure out what went wrong. | ||
|
|
||
| <!-- |
| this guide demonstrates how a user can self-host an RPC URL for use by themselves and others. | ||
|
|
||
| <!-- | ||
| Plan: |
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.
conorsch
force-pushed
the
docs-node-tutorial
branch
from
c00ee9a
to
c9f0903
Compare
1 task
conorsch
added a commit
that referenced
this pull request
Jul 5, 2024
conorsch
added a commit
that referenced
this pull request
Jul 5, 2024
## 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 <[email protected]>
conorsch
added a commit
that referenced
this pull request
Jul 25, 2024
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.
1 task
conorsch
added a commit
that referenced
this pull request
Jul 25, 2024
## 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 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: