[Polkadot WIki Migration] Set up a RPC node #32
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
Collaborator
CrackTheCode016
commented
Sep 17, 2024
CrackTheCode016
commented
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Scan for Vale false positives. Resolved convos = made it on the update list and should go away now. I left comments for the legit flags with suggested edits. Thank you! |
0xLucca
reviewed
Sep 30, 2024
lovelaced
reviewed
Oct 2, 2024
0xLucca
approved these changes
Oct 2, 2024
eshaben
reviewed
Oct 3, 2024
| @@ -1,3 +1,4 @@ | |||
| title: General Infrastructure | |||
| nav: | |||
| - index.md | |||
| - setup-rpc.md | |||
There was a problem hiding this comment.
Suggested change
| - setup-rpc.md | |
| - 'Set Up an RPC Node': setup-rpc.md |
| @@ -0,0 +1,66 @@ | |||
| --- | |||
| title: Set Up an RPC Node | |||
| description: Learn how to securely configure, connect to, and maintain a Polkadot SDK-based RPC node in an archival or pruned state. | |||
There was a problem hiding this comment.
Suggested change
| description: Learn how to securely configure, connect to, and maintain a Polkadot SDK-based RPC node in an archival or pruned state. | |
| description: Learn how to securely configure, connect to, and maintain an RPC node for a Polkadot SDK-based blockchain in an archival or pruned state. |
This was a tad bit short
| For an externally accessible Polkadot archive RPC node: | ||
|
|
||
| ```config | ||
| polkadot --chain polkadot --name myrpc --state-pruning archive --blocks-pruning archive --rpc-max-connections 100 --rpc-cors all --rpc-methods Safe --rpc-port 9944 |
There was a problem hiding this comment.
Suggested change
| polkadot --chain polkadot --name myrpc --state-pruning archive --blocks-pruning archive --rpc-max-connections 100 --rpc-cors all --rpc-methods Safe --rpc-port 9944 | |
| polkadot --chain polkadot \ | |
| --name INSERT_YOUR_NODE_NAME \ | |
| --state-pruning archive \ | |
| --blocks-pruning archive \ | |
| --rpc-cors all \ | |
| --rpc-methods safe |
I just removed the few that were set to default values
| For a Polkadot pruned RPC node: | ||
|
|
||
| ```config | ||
| polkadot --chain polkadot --name myrpc --state-pruning 1000 --blocks-pruning archive --rpc-max-connections 100 --rpc-cors all --rpc-methods Safe --rpc-port 9944 |
There was a problem hiding this comment.
Suggested change
| polkadot --chain polkadot --name myrpc --state-pruning 1000 --blocks-pruning archive --rpc-max-connections 100 --rpc-cors all --rpc-methods Safe --rpc-port 9944 | |
| polkadot --chain polkadot \ | |
| --name INSERT_YOUR_NODE_NAME \ | |
| --state-pruning 1000 \ | |
| --blocks-pruning archive \ | |
| --rpc-cors all \ | |
| --rpc-methods safe |
Comment on lines
+48
to
+52
| - You can limit the methods to use with `--rpc-methods`, an easy way to set this to a safe | ||
| mode is `--rpc-methods Safe` | ||
| - You can set your maximum connections through `--rpc-max-connections`, for example | ||
| `--rpc-max-connections 100` | ||
| - By default, localhost and Polkadot.js can access the RPC server. You can change this by setting `--rpc-cors`. To allow access from everywhere you can use `--rpc-cors all` |
There was a problem hiding this comment.
Suggested change
| - You can limit the methods to use with `--rpc-methods`, an easy way to set this to a safe | |
| mode is `--rpc-methods Safe` | |
| - You can set your maximum connections through `--rpc-max-connections`, for example | |
| `--rpc-max-connections 100` | |
| - By default, localhost and Polkadot.js can access the RPC server. You can change this by setting `--rpc-cors`. To allow access from everywhere you can use `--rpc-cors all` | |
| - You can limit the methods to use with `--rpc-methods`; an easy way to set this to a safe mode is `--rpc-methods safe` | |
| - You can set your maximum connections through `--rpc-max-connections`, for example, `--rpc-max-connections 200` | |
| - By default, localhost and Polkadot.js can access the RPC server. You can change this by setting `--rpc-cors`. To allow access from everywhere, you can use `--rpc-cors all` |
100 is the default so just changed it to another value
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.