Customizing your setup
If the script we provide isn't flexible enough for your needs, in this section you will find more ways to customize your setup.
The script uses sensible defaults, so for the majority of use cases the above is all that is required to run a node as validator. However, there are a few things you can customize, should you be so inclined.
If you want to tweak more advanced parameters, you can do so by editing the
env/archivistif you are running an archivist) file that you will find in the
aleph-node-runnerdirectory. Please note, however, that by doing so you may render your node non-functional, so proceed with care.
If you have a Docker image that you would like to use in place of the one downloaded by the script, you can provide its name and tag to the
./run_node.sh --name <your node's name> --image <your_image>:<tag>
By default, the node will start configured to be used as a validator. If you’re reading this guide, this is probably the desired setup. If, however, you would like to start an archivist, you can supply the
The script will auto-update the version each time you run it, so there's no need to manually provide the version. This is due to the fact that running an up-to-date version of the node is crucial for being able to validate without problems.
You might choose to only fetch the required files and Docker images by running the script with the
--build_onlyflag. When you have already downloaded the prerequisites, the script will make sure not to re-download them needlessly, so you can safely re-run it.
The node will start with telemetry enabled by default. This is the recommended setup and makes it much easier to see the health of the nodes in the network. However, if you want to disable the telemetry, you will need to set the