From b2353062529257f293bfc944d2ea09791c5f8d63 Mon Sep 17 00:00:00 2001 From: mik-tf Date: Mon, 23 Sep 2024 10:29:54 -0400 Subject: [PATCH] fixed typos --- collections/dashboard/solutions/nextcloud.md | 6 +++--- .../developers/grid_deployment/grid_deployment_full_vm.md | 8 ++++++-- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/collections/dashboard/solutions/nextcloud.md b/collections/dashboard/solutions/nextcloud.md index da22681..19b9ea4 100644 --- a/collections/dashboard/solutions/nextcloud.md +++ b/collections/dashboard/solutions/nextcloud.md @@ -170,7 +170,7 @@ In this section, we cover how to make a BorgBackup on the Nextcloud VM and we al In the section **Backup and restore**, you can set a [BorgBackup](https://www.borgbackup.org/) of your Nextcloud instance. -* Add a mount point and a directory name for your backup (e.g. **/mnt/backup**) and click **Submit backup location**. +* Add a mount point and a directory name for your backup (e.g. **/mnt/data/backup**) and click **Submit backup location**. * After the creation of the backup location, write down the **encryption password for backups** somewhere safe and offline. * Click **Create backup** to create a BorgBackup of your Nextcloud instance. * This will stop all containers, run the backup container and create the backup. @@ -188,7 +188,7 @@ After the first manual backup of your Nextcloud instance is complete, you can se To allow for another layer of redundancy, you can set a secondary VM on the grid and make a daily backup from the BorgBackup of your Nextcloud instance to the secondary VM. The following shows how to do this. It is based on the [File Transfer section](system_administrators@@file_transfer) of the manual. -For the following, we take into account that the BorgBackup is located at `/mnt/backup` on the VM running Nextcloud. +For the following, we take into account that the BorgBackup is located at `/mnt/data/backup` on the VM running Nextcloud. You will need to deploy a full VM on the TFGrid and SSH into this secondary VM. @@ -249,7 +249,7 @@ nano /root/rsync_nextcloud_backup.sh ``` #!/bin/bash -sudo rsync -avz --progress --delete --log-file=/root/nextcloud_backup/rsync_nextcloud_storage.log /root/nextcloud_backup/ root@:/mnt/backup +sudo rsync -avz --progress --delete --log-file=/root/nextcloud_backup/rsync_nextcloud_storage.log root@:/mnt/data/backup /root/nextcloud_backup/ ``` * Give permission to execute the script ``` diff --git a/collections/developers/grid_deployment/grid_deployment_full_vm.md b/collections/developers/grid_deployment/grid_deployment_full_vm.md index 2c739a4..fb930d5 100644 --- a/collections/developers/grid_deployment/grid_deployment_full_vm.md +++ b/collections/developers/grid_deployment/grid_deployment_full_vm.md @@ -71,6 +71,10 @@ 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. +- Set the prerequisites + ``` + apt update && apt install -y git nano ufw + ``` - Download the ThreeFold Tech `grid_deployment` repository ``` git clone https://github.com/threefoldtech/grid_deployment @@ -79,8 +83,8 @@ If you are deploying on testnet or devnet, simply replace `mainnet` by the prope - 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. ``` - echo .subkey_mainnet >> .gitignore - ../subkey generate-node-key > .nodekey_mainnet + echo .nodekey_mainnet >> .gitignore + ../../apps/subkey generate-node-key > .nodekey_mainnet cat .nodekey_mainnet ``` - Create and the set environment variables file -- 2.40.1