tfgrid/info_tfgrid
30
3
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Activity

Merge pull request 'fixed hero mdbook parsing' (#146) from development_update3 into development

Browse Source 
Reviewed-on: #146
This commit is contained in:
mik-tf 2024-09-23 14:42:37 +00:00
commit 75fa508b0e
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
collections/developers/grid_deployment/grid_deployment_full_vm.md
View File

@ -72,29 +72,29 @@ We show the steps to prepare the VM to run the network instance.
If you are deploying on testnet or devnet, simply replace `mainnet` by the proper network in the following lines. If you are deploying on testnet or devnet, simply replace `mainnet` by the proper network in the following lines.
- Set the prerequisites - Set the prerequisites
``` ```
apt update && apt install -y git nano ufw apt update && apt install -y git nano ufw
``` ```
- Download the ThreeFold Tech `grid_deployment` repository - Download the ThreeFold Tech `grid_deployment` repository
``` ```
git clone https://github.com/threefoldtech/grid_deployment git clone https://github.com/threefoldtech/grid_deployment
cd grid_deployment/docker-compose/mainnet cd grid_deployment/docker-compose/mainnet
``` ```
- Generate a TFChain node key with `subkey` - Generate a TFChain node key with `subkey`
- Note: If you deploy the 3 network instances, you can use the same node key for all 3 networks. But it is recommended to use 3 different keys to facilitate management. - Note: If you deploy the 3 network instances, you can use the same node key for all 3 networks. But it is recommended to use 3 different keys to facilitate management.
``` ```
echo .nodekey_mainnet >> .gitignore echo .nodekey_mainnet >> .gitignore
../../apps/subkey generate-node-key > .nodekey_mainnet ../../apps/subkey generate-node-key > .nodekey_mainnet
cat .nodekey_mainnet cat .nodekey_mainnet
``` ```
- Create and the set environment variables file - Create and the set environment variables file
``` ```
cp .secrets.env-example .secrets.env cp .secrets.env-example .secrets.env
``` ```
- Adjust the environment file - Adjust the environment file
``` ```
nano .secrets.env nano .secrets.env
``` ```
- To adjust the `.secrets.env` file, take into account the following: - To adjust the `.secrets.env` file, take into account the following:
- **DOMAIN**="example.com" - **DOMAIN**="example.com"
- Write your own domain - Write your own domain