tfgrid/info_tfgrid
33
3
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Activity

manual set urls for external collection

Browse Source
This commit is contained in:
Mik-TF
2024-05-13 19:10:10 -04:00
parent a4efec1aa3
commit 280652166f
40 changed files with 79 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
collections/system_administrators/terraform/advanced/terraform_nextcloud_vpn.md
View File

@@ -263,9 +263,9 @@ Note that, at any moment, if you want to see the information on your Terraform d
# Nextcloud Setup
* Access Nextcloud Setup
* Once you've deployed Nextcloud, you can access the Nextcloud Setup page by pasting on a browser the URL displayed on the line `fqdn = "..."` of the `terraform show` output. For more information on this, [read this documentation](../../../dashboard/solutions/nextcloud.md#nextcloud-setup).
* Once you've deployed Nextcloud, you can access the Nextcloud Setup page by pasting on a browser the URL displayed on the line `fqdn = "..."` of the `terraform show` output. For more information on this, [read this documentation](dashboard@@nextcloud).
* Create a backup and set a daily backup and update
* Make sure to create a backup with `/mnt/backup` as the mount point, and set a daily update and backup for your Nextcloud VM. For more information, [read this documentation](../../../dashboard/solutions/nextcloud.md#backups-and-updates).
* Make sure to create a backup with `/mnt/backup` as the mount point, and set a daily update and backup for your Nextcloud VM. For more information, [read this documentation](dashboard@@nextcloud).
> Note: By default, the daily Borgbackup is set at 4:00 UTC. If you change this parameter, make sure to adjust the moment the [Rsync backup](#create-a-cron-job-for-the-rsync-daily-backup) is done.

2
collections/system_administrators/terraform/resources/terraform_vm.md
View File

@@ -163,7 +163,7 @@ It's bit long for sure but let's try to dissect it a bit
ip_range = lookup(grid_network.net1.nodes_ip_range, 2, "")
```
- `node = grid_scheduler.sched.nodes["node1"]` means this deployment will happen on node returned from the scheduler. Otherwise the user can specify the node as `node = 2` and in this case the choice of the node is completely up to the user at this point. They need to do the capacity planning. Check the [Node Finder](../../../dashboard/deploy/node_finder.md) to know which nodes fits your deployment criteria.
- `node = grid_scheduler.sched.nodes["node1"]` means this deployment will happen on node returned from the scheduler. Otherwise the user can specify the node as `node = 2` and in this case the choice of the node is completely up to the user at this point. They need to do the capacity planning. Check the [Node Finder](dashboard@@node_finder) to know which nodes fits your deployment criteria.
- `network_name` which network to deploy our project on, and here we choose the `name` of network `net1`
- `ip_range` here we [lookup](https://www.terraform.io/docs/language/functions/lookup.html) the iprange of node `2` and initially load it with `""`

4
collections/system_administrators/terraform/terraform_basics.md
View File

@@ -51,7 +51,7 @@ There are two options when it comes to finding a node to deploy on. You can use
- Use the [scheduler](resources/terraform_scheduler.md)
- Scheduler will help you find a node that matches your criteria
- Use the Nodes Explorer
- You can check the [Node Finder](../../dashboard/deploy/node_finder.md) to know which nodes fits your deployment criteria.
- You can check the [Node Finder](dashboard@@node_finder) to know which nodes fits your deployment criteria.
- Make sure you choose a node which has enough capacity and is available (up and running).
## Preparation
@@ -160,7 +160,7 @@ terraform destroy
## Available Flists
You can consult the [list of Flists](../../developers/flist/flist.md) to learn more about the available Flist to use with a virtual machine.
You can consult the [list of Flists](developers@@flist) to learn more about the available Flist to use with a virtual machine.
## Full and Micro Virtual Machines