Infra > Running a Node > Set Up a Full Node #164
Conversation
| A pruned node only keeps a limited number of finalized blocks of the network, not its complete history. State and block pruning are two ways of removing old blocks from a system. State pruning removes the states of old blocks while preserving block headers. Block pruning removes the block bodies of old blocks while retaining block headers. You can complete many frequently required actions with a pruned node, such as displaying account balances, making transfers, setting up session keys, and staking. | ||
|
|
||
| ## Setup Instructions |
There was a problem hiding this comment.
Some of this content needs to be revisited, as it includes instructions for installing the polkadot binary and that should be a separate guide
| Command-line flags passed to the binary can be customized by editing `/etc/default/polkadot`. This file will not be overwritten on updating `polkadot`. | ||
|
|
||
| ### Debian-based (Debian, Ubuntu) |
There was a problem hiding this comment.
This is confusing - why are there steps for each of the operating systems above and then these sections as well?
| -p 9944:9944 \ | ||
| -p 9615:9615 parity/polkadot:v0.9.13 \ | ||
| --name "calling_home_from_a_docker_container" \ |
There was a problem hiding this comment.
for name, we should just default to INSERT_YOUR_NODE_NAME
| polkadot --chain polkadot \ | ||
| --name INSERT_YOUR_NODE_NAME \ | ||
| --state-pruning archive \ | ||
| --blocks-pruning archive \ | ||
| --rpc-cors all \ | ||
| --rpc-methods safe | ||
| ``` | ||
|
|
||
| For an externally accessible Polkadot pruned node run: | ||
|
|
||
| ```bash | ||
| polkadot --chain polkadot \ | ||
| --name INSERT_YOUR_NODE_NAME \ | ||
| --state-pruning 1000 \ | ||
| --blocks-pruning archive \ | ||
| --rpc-cors all \ | ||
| --rpc-methods safe | ||
| ``` |
There was a problem hiding this comment.
These aren't Docker commands. But ideally, we should have the start up commands in tabs
| ## Secure the WebSocket Port | ||
|
|
||
| To securely access your WebSocket (WS) connection over an SSL-enabled connection (necessary for SSL-enabled developer consoles), you'll need to convert the WS connection to a secure WSS connection. You can complete this conversion using a proxy and an SSL certificate. For detailed steps on setting this up, refer to the [Set Up Secure WebSockets](TODO: add path){target=\_blank} guide. |
There was a problem hiding this comment.
We're not going to have docs on Securing WebSockets, so this link can be removed
| ``` | ||
|
|
||
| Use the `--help` flag to determine which flags you can use when running the node. For example, if you want to connect to your node remotely, you'll probably want to use `--rpc-external` and `--rpc-cors all`. |
There was a problem hiding this comment.
This should probably be added after we provide the start up commands. It'd be more useful at that point
| Use the `--help` flag to determine which flags you can use when running the node. For example, if you want to connect to your node remotely, you'll probably want to use `--rpc-external` and `--rpc-cors all`. | ||
|
|
||
| The syncing process will take a while, depending on your capacity, processing power, disk speed, and RAM. For example, the process can be completed on a $10 DigitalOcean droplet in ~36 hours. Once it is synced, you may find it in [Telemetry](https://telemetry.polkadot.io/#list/Polkadot){target=_blank}. |
There was a problem hiding this comment.
This should be after the start up command as well, this isn't really related to Connect to the Node
Co-authored-by: Erin Shaben <[email protected]>
|
Took a lot of stuff out and this is what's left for the page. I'm confused about the goal of this page and not sure now what should even be on it. |
|
Closing this as it's part of the #45 now |
This PR: