⌨️Setting up your Node
Now that you have the ways to contribute to the open source project, let's make sure that you know how to do it.
System requirements
To successfully deploy a node, you need the follow at minimum:
Operating System
Mac, Linux, Windows (will need WSL)
GPU
Optional
Processor
2 core vCPUs
RAM
8GB
Storage
10GB of free space
Network
Internet
Node Installation Quick Start
Install the one-line script to download the latest version of the GaiaNet node
Initialize the node using the configuration options in
$HOME/gaianet/config.json
:gaianet init
(By default, GaiaNet is initialized with a Phi-3 LLM and a Paris knowledge base.)
Start your node:
gaianet start
Upon a successful start, the command will print a public UPL for the node. Open a browser tab to that URL to see the node information and chat with the AI agent on the node.
To stop the node: gaianet stop
OpenAI API Replacement
After your node is created, you can use it as a an OpenAI compatible web service. By simply opening the node's dashboard and pasting the node's public URL into the browser, the dashboard will display a table providing all parameters needing to be replaced.
Starting a node with Docker
To quickly start a node using Docker, run this command:
Docker Node Installation with NVIDIA CUDA 12 machine
You'll know your node is ready when the console shows The GaiaNet node is started at: https://...
. To interact with the node, open that URL in a browser window.
Stopping and restarting your node
Considerations for restarting node
Each time the node is restarted, the vector collection (knowledge base) will be re-initialized. Additionally, when the node is restarted, the log messages are no longer printed to the console.
They can still be seen by logging into the container:
Deleting your node
If your node is no longer needed, it can simply be deleted by running these commands:
Configuring your node
Making Changes
The configuration parameters of the node can be updated by executing the config
command on the gaianet
program within the container.
After all the necessary commands are run to make the changes, the node must be restarted for the new configuration to take effect.
Changing the node ID
The node ID (Ethereum address) associated with is easily updated.
Start the node
Copy the
nodeid.json
file and the keystore file defined innodeid.json
into the container.
Restart the node for the new address and keystore to take effect.
Publishing your node for others to use
Now that you've completed the node installation, you can get started on building your plugins and integrations!
Last updated