Hotfix Trusted Hash Instructions for Node Operators #1273
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
Based on a Slack conversation, the `trusted_hash` information in the Installing a Node document needs to be updated.
|
The NODE_ADDR and PROTOCOL need to be commands that are issues above the sudo sed to pull the hash. They all need to exist in the same section. |
sacherjj
reviewed
Sep 1, 2023
sacherjj
reviewed
Sep 1, 2023
ipopescu
approved these changes
Sep 1, 2023
Co-authored-by: Joe Sacher <[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.
What does this PR fix/introduce?
Based on a Slack conversation, the
trusted_hashinformation in the Installing a Node document needs to be updated.Additional context
Slack Conversation
Checklist
(Delete any that aren't relevant)
yarn install && yarn run build.Reviewers
@sacherjj