- Run
gladius-control
to start the server- Expected Output:
$ gladius-control Running at http://localhost:3000
- Leave this running in a new window for the CLI to communicate
- Expected Output:
- Run
gladius-edge
to start the server- Expected Output:
$ gladius-edge Running - Use "gladius-node start" to start it
- Leave this running in a new window for the CLI to communicate
- Expected Output:
- Set up a local static IP for the machine you will be running the Gladius node on
- Forward port 8080 on your router to that machine, and make sure you enable hairpin nat (so you can access websites you protect)
- Warning: Make sure port 3000 and 5000 are not accesible from the outside!
- Create a new Ethereum wallet
- Acquire 1 Ether on the Ropsten testnet (or go here if you're using Metamask)
- Run
gladius-node init
and fill out the requested information (use the same email that you applied for the beta with)
After you execute a command it will suggest the next logical command. For example, after init
you can run gladius-node create
to create a new Node. As of now the Node manager only supports 1 Node per user therefore if you run gladius-node create
multiple times you will keep overwriting your current node.
The gladius-cli
acts as an interface for a user to interact with the gladius-control-daemon
and the gladius-edge-daemon
. Therefore, if you want to use the CLI you must have both of the daemons running either in the background or on seperate terminal windows. Both daemons run servers on your machine once you start them. If you no longer want them to be running simply exit the window or stop the processes. This will stop the servers and if you want to use the CLI you'll have to start them again.
If you need help port forwarding or setting up a local ip lots of resources can be found by searching the Internet about router specific instructions
For a full list of commands, please see the gladius-cli repository