--restart always -dinstead of
-ito make sure your node restart when docker is started (i.e. when your server boots).
nodlefolder that you must have previously created according to our instructions via
-v $(pwd)/nodle:/datain order to persist the chain's data on your server even between restarts and thus make sure you do not have to resync the whole blockchain every time your container restart.
-p 9944:9944 -p 30333:30333.
--ws-external --rpc-cors allin order to make sure you can query your node as intended. Indeed, because we run inside a docker container some basic sanity checks won't work and need to be disabled.
--chain main, if you wanted to sync with our test network you could replace it with
--chainflag, for instance, to sync with our test network you could use
Configuring your server to have the node start every time the server boots is outside of the scope of this wiki, however you could do so via
--pruning=archive, we typically use it on our own public nodes.
--wasm-execution compiledto synchronize with the chain networks faster (we often have a 10x boost when using it). This is typically available and well supported on machines with a
x86_64architecture. We didn't include it in the previously listed commands to avoid any potential bugs or crashes as it may not work as well with less traditional servers; but if you can use it you definitely should!
--nameflag. For instance you could use
--name "This is my first Nodle Chain full node".