Skip to main content

Quick start MCC

This tutorial will guide you through installing Staex (MCC only) in your network. This setup uses user certificate that is signed by Staex and auto-generated node private keys signed by the user certificate. Nodes trust each other only when their keys were signed by trusted user certificate. This setup is your go-to approach for secure deployment of Staex in a real-world scenario. Please, refer to Getting user certificate to learn how to get your user certificate. Please, refer to Generating node certificate to learn how to generate your node's private key and certificate.

caution

All nodes in the network have to have the same user certificate stored under /etc/mcc/user_cert path to trust each other.

Install MCC​

Use a package manager from your Linux distribution to install our software. Alternatively, unpack the software into /opt/mcc directory.

apt install ./mcc*.deb

Configure system service​

If you are installing Staex on a node in a local area network, add the address of the bootnode (usually a node with a public IP address) in /etc/mcc/mcc.yaml file.

boot: IP:9376
# Please, replace IP with the public IP address of the bootnode.

Please, refer to configure bootnodes if you have complex network infrastructure.

Then issue the following commands to start Staex service immediately and on system boot.

systemctl enable mcc --now
If everything went successfully, the following commands will report that the service are active and running.
systemctl status mcc

In order to read StaexMCC logs use the following commands.

journalctl -u mcc -e

Where to go from here​

Now that you have installed Staex you can proceed to configure bootnodes if you have complex network infrastructure.