manual, set internal collections to filename.md template

This commit is contained in:
Mik-TF
2024-05-13 19:28:23 -04:00
parent 280652166f
commit 1836179a75
169 changed files with 709 additions and 709 deletions

View File

@@ -4,7 +4,7 @@ SSH is a secure protocol used as the primary means of connecting to Linux server
<h2> Table of Contents </h2>
- [SSH with OpenSSH](./ssh_openssh.md)
- [SSH with PuTTY](./ssh_putty.md)
- [SSH with WSL](./ssh_wsl.md)
- [WireGuard Access](./ssh_wireguard.md)
- [SSH with OpenSSH](ssh_openssh.md)
- [SSH with PuTTY](ssh_putty.md)
- [SSH with WSL](ssh_wsl.md)
- [WireGuard Access](ssh_wireguard.md)

View File

@@ -20,7 +20,7 @@
# Introduction
In this Threefold Guide, we show how easy it is to deploy a full virtual machine (VM) and SSH into a 3Node with [OpenSSH](https://www.openssh.com/) on Linux, MAC and Windows with both an IPv4 and a Planetary Network connection. To connect to the 3Node with WireGuard, read [this documentation](./ssh_wireguard.md).
In this Threefold Guide, we show how easy it is to deploy a full virtual machine (VM) and SSH into a 3Node with [OpenSSH](https://www.openssh.com/) on Linux, MAC and Windows with both an IPv4 and a Planetary Network connection. To connect to the 3Node with WireGuard, read [this documentation](ssh_wireguard.md).
To deploy different workloads, the SSH connection process should be very similar.

View File

@@ -19,7 +19,7 @@
In this Threefold Guide, we show how to set up [WireGuard](https://www.wireguard.com/) to access a 3Node deployment with an SSH connection.
Note that WireGuard provides the connection to the 3Node deployment. It is up to you to decide which SSH client you want to use. This means that the steps to SSH into a 3Node deployment will be similar to the steps proposed in the guides for [Open-SSH](./ssh_openssh.md), [PuTTy](ssh_putty.md) and [WSL](./ssh_wsl.md). Please refer to [this documentation](./ssh_guide.md) if you have any questions concerning SSH clients. The main difference will be that we connect to the 3Node deployment using a WireGuard connection instead of an IPv4 or a Planetary Network connection.
Note that WireGuard provides the connection to the 3Node deployment. It is up to you to decide which SSH client you want to use. This means that the steps to SSH into a 3Node deployment will be similar to the steps proposed in the guides for [Open-SSH](ssh_openssh.md), [PuTTy](ssh_putty.md) and [WSL](ssh_wsl.md). Please refer to [this documentation](ssh_guide.md) if you have any questions concerning SSH clients. The main difference will be that we connect to the 3Node deployment using a WireGuard connection instead of an IPv4 or a Planetary Network connection.
@@ -28,15 +28,15 @@ Note that WireGuard provides the connection to the 3Node deployment. It is up to
Make sure to [read the introduction](../tfgrid3_getstarted.md#get-started---your-first-deployment) before going further.
* SSH client of your choice
* [Open-SSH](./ssh_openssh.md)
* [Open-SSH](ssh_openssh.md)
* [PuTTy](ssh_putty.md)
* [WSL](./ssh_wsl.md)
* [WSL](ssh_wsl.md)
# Deploy a Weblet with WireGuard Access
For this guide on WireGuard access, we deploy a [Full VM](../../../dashboard/solutions/fullVm.md). Note that the whole process is similar with other types of ThreeFold weblets on the Dashboard.
For this guide on WireGuard access, we deploy a [Full VM](fullVm.md). Note that the whole process is similar with other types of ThreeFold weblets on the Dashboard.
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
* Choose the parameters you want