You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: node-infrastructure/run-a-collator/collator.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -308,7 +308,9 @@ Sync time depends on:
308
308
309
309
The relay chain uses warp sync for faster synchronization.
310
310
311
-
**Important**: Do not proceed with registration until both chains are fully synced. Monitor sync progress using the log viewing commands in the [Log Management](#log-management) section.
311
+
!!! warning
312
+
313
+
Do not proceed with registration until both chains are fully synced. Monitor sync progress using the log viewing commands in the [Log Management](#log-management) section.
For non-system parachains, check the parachain's documentation for official chain specification files.
47
47
48
-
**Note**: Throughout this guide, we use **People Chain** as the example. To set up a different parachain, substitute the chain spec file, snapshot path, and chain name with values for your target parachain.
48
+
!!! note
49
+
50
+
Throughout this guide, we use **People Chain** as the example. To set up a different parachain, substitute the chain spec file, snapshot path, and chain name with values for your target parachain.
- Consider DDoS protection and rate limiting for production deployments
73
75
74
-
**Note**: For development or low-traffic scenarios, you can reduce these requirements proportionally. Consider using a reverse proxy (nginx, Caddy) for production deployments.
76
+
!!! note
77
+
78
+
For development or low-traffic scenarios, you can reduce these requirements proportionally. Consider using a reverse proxy (nginx, Caddy) for production deployments.
75
79
76
80
### Software Requirements
77
81
@@ -102,7 +106,9 @@ Using pre-synchronized snapshots significantly reduces initial sync time from se
**Note**: Snapshots are available for system parachains and the Polkadot relay chain. For other parachains, check with the parachain team for snapshot availability or sync from genesis.
109
+
!!! note
110
+
111
+
Snapshots are available for system parachains and the Polkadot relay chain. For other parachains, check with the parachain team for snapshot availability or sync from genesis.
106
112
107
113
#### Create Directories
108
114
@@ -139,7 +145,9 @@ rm files.txt
139
145
-`--retries-sleep 10s`: Waits 10 seconds between retry attempts
140
146
-`--size-only`: Only transfers if sizes differ (prevents unnecessary re-downloads)
141
147
142
-
**Note**: If a snapshot is not available, you can sync from scratch (which will take longer) or check https://snapshots.polkadot.io/ for alternative snapshot providers.
148
+
!!! note
149
+
150
+
If a snapshot is not available, you can sync from scratch (which will take longer) or check https://snapshots.polkadot.io/ for alternative snapshot providers.
143
151
144
152
#### Download Polkadot Relay Chain Snapshot
145
153
@@ -171,7 +179,9 @@ Launch the node using the official Parity Docker image.
**Note**: The `parity/polkadot-parachain` image works for system parachains and parachains built with standard Cumulus templates. For parachains with custom runtimes, check the parachain's documentation for their specific Docker image or binary.
182
+
!!! note
183
+
184
+
The `parity/polkadot-parachain` image works for system parachains and parachains built with standard Cumulus templates. For parachains with custom runtimes, check the parachain's documentation for their specific Docker image or binary.
175
185
176
186
```bash
177
187
docker run -d --name people-chain-rpc --restart unless-stopped \
@@ -334,7 +344,9 @@ docker start people-chain-rpc
334
344
docker rm people-chain-rpc
335
345
```
336
346
337
-
**Note**: For update procedures, see the [Updates and Upgrades](#updates-and-upgrades) section.
347
+
!!! note
348
+
349
+
For update procedures, see the [Updates and Upgrades](#updates-and-upgrades) section.
0 commit comments