Spin-up a Dijets Node in minutes using the installer script

Run a Dijets Node Using the Install Script

The installer script is a shell (bash) script that installs DijetsNodeGo on your computer. This script sets up full, running node in a matter of minutes with minimal user input required.

This installer script assumes that:

• DijetsNodeGo is not running and not already installed as a service
• User running the script has superuser privileges (can run sudo)

Environment Considerations#

This script has primarily been developed for and tested for Ubuntu 20.04 upwards. If you run a different flavor of Linux than the script might not work as intended. It assumes systemd is used to run system services. Other Linux flavors might use something else, or might have files in different places than is assumed by the script.

Node Running from Terminal

If you already have a Dijets node running in a terminal stop it by pressing ctrl+C.

Node Running as a Service

If your node is already running as a service, then you probably don't need this script. You're already good to go.

Node Running in the Background

If your node is running in the background (by running with nohup, for example) then find the process running the node by running ps aux | grep dijets. This will produce output like:

Look for line that doesn't have grep on it. In this example, that is the second line. It shows information about your node. Note the process id, in this case, 1189. Stop the node by running kill -2 1189.

Node Working Files

If you previously ran a DijetsNodeGo node on this computer, you will have local node files stored in $HOME/.dijetsnodego directory. Those files will not be disturbed, and node set up by the script will continue operation with the same identity and state it had before. That being said, for your node's security, back up any private keys for staking, found in $HOME/.dijetsnodego/staking folder and store them somewhere secure. You can use those files to recreate your node on a different computer if you ever need to. Check out the tutorial on Node Backup for backup and restore procedure.

Networking Considerations#

To run successfully, DijetsNodeGo needs to accept connections from the Internet on the network port 9651. Before you proceed with the installation, you need to determine the networking environment your node will run in.

Running on a Cloud Provider

If your node is running on a cloud provider computer instance, it will have a static IP. Find out what that static IP is, or set it up if you haven't done so already. The script will try to find out the IP by itself, but that might not work in all environments, so you will need to check the IP or enter it yourself.

Running on a Home Connection

If you're running a node on a computer that is on a residential internet connection, then you more than likely have a dynamic IP; that is, your IP will change periodically. The install script will configure the node appropriately for that situation. But, for a home connection, you will need to set up inbound port forwarding of port 9651 from the internet to the computer the node is installed on.

Alternatively you can ask your ISP to provide you with a static IP.

Running the Script#

To download and run the script, enter the following in the terminal:

The above commands start the Node installation process. The output should look something like this:

And then the script will prompt you for information about the network environment:

Enter 1 if you have a dynamic IP, and 2 if you have a static IP.

Confirm with y, or n if the detected IP is wrong (or empty), and then enter the correct IP at the next prompt.

Next, you have to set up RPC port access for your node. Those are used to query the node for its internal state, to send commands to the node, or to interact with the platform and its chains (sending transactions, for example). You will be prompted with:

local This setting only allows RPC requests from the node machine itself. any This setting allows you to send RPC requests to your node from a remote machine.

The script will then continue with system service creation and finish with starting the service:

Post Installation#

DijetsNodeGo should be running in the background as a service. You can check that it's running with:

This will print the node's latest logs, which should look like this:

Note the active (running) which indicates the service is running OK. You may need to press q to return to the command prompt.

To find out your NodeID, which is used to identify your node to the network, run the following command:

It will produce output like:

Prepend DijetsNode- to the value you get, for example, DijetsNode-7S2JhkGp7yKPzwpfd7KNwcM217ZuMzPFT. Store that; it will be needed for staking or looking up your node.

Stopping the Node#

To stop DijetsNodeGo, run:

To start it again, run:

Advanced Node Configuration#

Without any additional arguments, the script installs the node in a most common configuration. But the script also enables various advanced options to be configured, via the command line prompts. Following is a list of advanced options and their usage:

• admin - Admin API will be enabled
• archival - disables database pruning and preserves the complete transaction history
• state-sync - if on state-sync for the Utility Chain is used, if off it will use regular transaction replay to bootstrap; state-sync is much faster, but has no historical data
• db-dir - used to provide the full path to the location where the database will be stored
• testnet - node will connect to Dijets testnet instead of the Mainnet
• index - Index API will be enabled
• ip - use dynamic, static arguments, of enter a desired IP directly to be used as the public IP node will advertise to the network
• rpc - use any or local argument to select any or local network interface to be used to listen for RPC calls

Please note that configuring index and archival options on an existing node will require a fresh bootstrap to recreate the database.

Complete script usage can be displayed by entering:

Unattended Installation#

If you want to use the script in an automated environment where you cannot enter the data at the prompts you must provide at least the rpc and ip options. For example:

Usage Examples#

To run a Mainnet node with indexing enabled and autodetected static IP:

To run an archival Mainnet node with dynamic IP and database located at /home/node/db:

To use Utility Chain state-sync to quickly bootstrap a Mainnet node, with dynamic IP and local RPC only:

Node Configuration#

File that configures node operation is ~/.dijetsnodego/configs/node.json. You can edit it to add or change configuration options. The documentation of configuration options can be found here. Configuration may look like this:

Note that configuration file needs to be a properly formatted JSON file, so switches are formatted differently than for command line, so don't enter options like --dynamic-public-ip=opendns but as in the example above.

Script also creates an empty Utility Chain config file, located at ~/.dijetsnodego/configs/chains/UC/config.json. By editing that file you can configure the Utility Chain. Click here to read about the chain configuration for Utility Chain.

What Next?#

That's it, you're running a Dijets node! Congratulations! Let us know how it went on our Twitter

If you have any questions, or need help, feel free to contact us on Dijets public support space on Qowalts

Feel free to interact with your node, stake your dijets, learn more about validators/delegators and how you can help secure the network and earn DJT or check your node's health by calling Healthcheck APIs to get a better insight into how your node is doing.

If you just want to issue commands to a Dijets Node and haven't gotten around to setting up your own node, you can always use our Postman Collection to issue API calls directly through the postman app or in your browser.

Finally, if you haven't already, it is always good practice to back up your files in case of a major issue or if you plan on changing your host machine.