manual removed files
This commit is contained in:
Binary file not shown.
|
Before Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 49 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 88 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 107 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 41 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 67 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 58 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 76 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 135 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 38 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 69 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 37 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 90 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB |
@@ -1,4 +0,0 @@
|
||||
# Threefold Connect Basics Tutorial
|
||||
|
||||
* Create an account
|
||||
* Create a wallet
|
||||
@@ -1,148 +0,0 @@
|
||||
<h1>ThreeFold Connect: Create a Threefold Connect Account and Wallet</h1>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Download the ThreeFold Connect App](#download-the-threefold-connect-app)
|
||||
- [Create a ThreeFold Connect Account](#create-a-threefold-connect-account)
|
||||
- [Verify Your Email](#verify-your-email)
|
||||
- [Create a ThreeFold Connect Wallet](#create-a-threefold-connect-wallet)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
The ThreeFold Connect app emerges as a dynamic and essential companion for individuals seeking seamless access to the ThreeFold ecosystem on the go. Available for free download on both iOS and Android mobile platforms, the TF Connect app ensures that users can effortlessly engage with the ThreeFold Grid, empowers users to manage their digital assets, engage in secure transactions, and explore decentralized financial opportunities, all within a unified mobile experience.
|
||||
|
||||
In this tutorial, we show you how to create a ThreeFold Connect account and wallet. The main steps are simple and you will be done in no time. If you have any questions, feel free to write a post on the [ThreeFold Forum](http://forum.threefold.io/).
|
||||
|
||||
## Download the ThreeFold Connect App
|
||||
|
||||
|
||||
The ThreeFold Connect app is available for [Android](https://play.google.com/store/apps/details?id=org.jimber.threebotlogin&hl=en&gl=US) and [iOS](https://apps.apple.com/us/app/threefold-connect/id1459845885).
|
||||
|
||||
- Note that for Android phones, you need at minimum Android 8.1
|
||||
- Note that for iOS phones, you need at minimum iOS 15
|
||||
|
||||
Either use the links above, or search for the ThreeFold Connect app on the App Store or the Google Play Store. Then install and open the app. If you want to leave a 5-star review of the app, no one here will stop you!
|
||||
|
||||
|
||||
|
||||
|
||||
When you try to open the app, if you get an error message such as: "Error in initialization in Flagsmith...", you might need to upgrade your phone to a newer software version (Android 8.1 and iOS 15).
|
||||
|
||||
***
|
||||
|
||||
## Create a ThreeFold Connect Account
|
||||
|
||||
Once you are in the app, you will see some introduction pages to help you familiarize with the TF Connect app. You will also be asked to read and accept ThreeFold's Terms and Conditions.
|
||||
|
||||
|
||||
|
||||
|
||||
You will then be asked to either *SIGN UP* or *RECOVER ACCOUNT*. To create a new account, click *SIGN UP*.
|
||||
|
||||
|
||||
|
||||
Then, choose a *ThreeFold Connect Id*. This 3bot ID will be used, as well as the seed phrase, when you want to recover an account. Choose wisely. And do not forget it! Here we will use TFExample, as an example.
|
||||
|
||||
|
||||
|
||||
Next, you need to add a valid email address. You will need to access your email and confirm the ThreeFold validation email to fully use the ThreeFold Connect app.
|
||||
|
||||
|
||||
|
||||
The next step is crucial! Make sure no one is around looking at your screen. You will be shown your seed phrase. Keep this in a secure and offline place. You will need the 3bot ID and the seed phrase to recover your account. This seed phrase is of utmost important. Do not lose it nor give it to anyone.
|
||||
|
||||
|
||||
|
||||
Once you've hit *Next*, you will be asked to write down 3 random words of your seed phrase. This is a necessary step to ensure you have taken the time to write down your seed phrase.
|
||||
|
||||
|
||||
|
||||
Then, you'll be asked to confirm your TF 3bot ID and the associated email.
|
||||
|
||||
|
||||
|
||||
Finally, you will be asked to choose a 4-digit pin. This will be needed to use the ThreeFold Connect app. If you ever forget this 4-digit pin, you will need to recover your account from your 3bot name and your seed phrase. You will need to confirm the new pin in the next step.
|
||||
|
||||
|
||||
|
||||
That's it! You've created your ThreeFold Connect account. You can press the hamburger menu on the top left to explore the ThreeFold Connect app.
|
||||
|
||||
|
||||
|
||||
In the next step, we will create a ThreeFold Connect wallet. You'll see, it's very simple!
|
||||
|
||||
But first, let's see how to verify your email.
|
||||
|
||||
***
|
||||
|
||||
## Verify Your Email
|
||||
|
||||
Once you've created your account, an email will be sent to the email address you've chosen in the account creation process. To verify your email, go on your email inbox and open the email sent by *info@openkyc.live* with the subject *Verify your email address*.
|
||||
|
||||
In this email, click on the link *Verify my email address*. This will lead you to a *login.threefold.me* link. The process should be automatic. Once this is done, you will receive a confirmation on screen, as well as on your phone.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If, for some reason, you did not receive the verification email, simply click on *Verify* and another email will be sent.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
That's it! You've now created a ThreeFold Connect account.
|
||||
|
||||
All that is left to do is to create a ThreeFold Connect wallet. This is very simple.
|
||||
|
||||
Let's go!
|
||||
|
||||
***
|
||||
|
||||
## Create a ThreeFold Connect Wallet
|
||||
|
||||
To create a wallet, click on the ThreeFold Connect app menu, then choose *Wallet*.
|
||||
|
||||
|
||||
|
||||
Once you are in the section *Wallet*, click on *Create Initial Wallet*. If it doesn't work the first time, retry some more. If you have trouble creating a wallet, make sure your connection is reliable. You can try a couple of minutes later if it still doesn't work. With a reliable connection, there shouldn't be any problem. Contact TF Support if problems persist.
|
||||
|
||||
|
||||
|
||||
This is what you see when the TF Grid is initializing your wallet.
|
||||
|
||||
|
||||
|
||||
Once your wallet is initialized, you will see *No balance found for this wallet*. You can click on this button to enter the wallet.
|
||||
|
||||
|
||||
|
||||
Once inside your wallet, this is what you see.
|
||||
|
||||
|
||||
|
||||
We will now see where the Stellar and the TFChain addresses and secrets are to be found. We will also change the wallet name. To do so, click on the *encircled i* at the bottom right of the screen.
|
||||
|
||||
On this page, you can access your Stellar and TFChain addresses as well as your Stellar and TFChain secret keys.
|
||||
|
||||
|
||||
|
||||
To change the name of your wallet, click on the button next to *Wallet Name*. Here we use TFWalletExample. Note that you can also use alphanumeric characters.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
At the top of the section *Wallet*, we can see that the name has changed.
|
||||
|
||||
|
||||
|
||||
That's it! You now have a ThreeFold Connect account and wallet.
|
||||
This will be very useful for your TFT transactions on the ThreeFold ecosystem.
|
||||
|
||||
***
|
||||
@@ -1,148 +0,0 @@
|
||||
<h1> Threefold Dashboard: Create Account and Transfer TFT </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Create Polkadot Extension Account](#create-polkadot-extension-account)
|
||||
- [Transfer TFT from Stellar Chain to TFChain](#transfer-tft-from-stellar-chain-to-tfchain)
|
||||
|
||||
## Introduction
|
||||
|
||||
For this section, we will create an account on the TFChain and transfer TFT from Stellar chain to TFChain. We will then be able to use the TFT and deploy workloads on the Threefold Playground.
|
||||
|
||||
## Create Polkadot Extension Account
|
||||
|
||||
Go to the Threefold Dashboard: [dashboard.grid.tf](https://dashboard.grid.tf/)
|
||||
|
||||
If you don't have the Polkadot extension installed on your browser, you will be able to click on the download link directly on the Threefold Dashboard page:
|
||||
|
||||
|
||||
|
||||
This link will lead you to the Polkadot extension download page: https://polkadot.js.org/extension/
|
||||
|
||||
|
||||
|
||||
Then, simply click on "Add to Chrome".
|
||||
|
||||
|
||||
|
||||
Then, confirm by clicking on "Add extension".
|
||||
|
||||
|
||||
|
||||
You can now access the extension by clicking on the browser's extension button on the top right of the screen, and by then clicking on *polkadot{.js} extension*:
|
||||
|
||||
|
||||
|
||||
Make sure to carefully read the Polkadot message then click on **Understood, let me continue**:
|
||||
|
||||
|
||||
|
||||
Then click on the **plus** symbol to create a new account:
|
||||
|
||||
|
||||
|
||||
For this next step, you should be very careful. Your seed phrase is your only access to your account. Make sure to keep a copy somewhere safe and offline.
|
||||
|
||||
|
||||
|
||||
After, choose a name for your account and a password:
|
||||
|
||||
|
||||
|
||||
Your account is now created. You can see it when you open the Polkadot extension on your browser:
|
||||
|
||||
|
||||
|
||||
Now, when you go on the [Threefold Dashboard](https://dashboard.grid.tf/), you can click on the **Connect** button on the top right corner:
|
||||
|
||||
|
||||
|
||||
You will then need to grant the Threefold Dashboard access to your Polkadot account.
|
||||
|
||||
|
||||
|
||||
Then, simply click on your account name to access the Threefold Dashboard:
|
||||
|
||||
|
||||
|
||||
Read and accept the Terms and Conditions
|
||||
|
||||
|
||||
|
||||
You will be asked to confirm the transaction, write your password and click on **Sign the transaction** to confirm.
|
||||
|
||||
|
||||
|
||||
Once you open your account, you can choose a relay for it then click on **Create**.
|
||||
|
||||
|
||||
|
||||
You will also be asked to confirm the transaction.
|
||||
|
||||
|
||||
|
||||
That's it! You've successfully created an account on the TFChain thanks to the Polkadot extension. You can now access the Threefold Dashboard.
|
||||
|
||||
On to the next section! Where we will transfer (or swap) TFT from the Stellar Chain on your Threefold Connect app wallet to the TFChain on the Threefold Dashboard.
|
||||
|
||||
You'll see, this is so easy thanks to the Threefold Dashboard configuration.
|
||||
|
||||
***
|
||||
|
||||
## Transfer TFT from Stellar Chain to TFChain
|
||||
|
||||
On the [Threefold Dashboard](https://dashboard.grid.tf/), click on the **Portal**, then click on **Swap**.
|
||||
|
||||
Make sure the chain **stellar** is selected. Then click **Deposit**, as we want to deposit TFT from the Stellar Chain to the TFChain.
|
||||
|
||||
|
||||
|
||||
Next, you will scan the QR code shown on the screen with the Threefold Connect app.
|
||||
|
||||
> Note that you can also manually enter the Stellar Chain address and the Twin ID.
|
||||
|
||||
|
||||
|
||||
To scan the QR code on the Threefold Connec app, follow those steps:
|
||||
|
||||
Click on the menu button:
|
||||
|
||||
|
||||
|
||||
Click on **Wallet**:
|
||||
|
||||
|
||||
|
||||
Then, click on **Send Coins**:
|
||||
|
||||
|
||||
|
||||
On the next page, select the **Stellar** chain, then click on **SCAN QR**:
|
||||
|
||||
|
||||
|
||||
|
||||
This will automatically write the correct address and twin ID.
|
||||
|
||||
You can now write the amount of TFT you wish to send, and then click **SEND**
|
||||
|
||||
> We recommend to try with a small amount of TFT first to make sure everything is OK.
|
||||
>
|
||||
> The transfer fees are of 1 TFT per transfer.
|
||||
|
||||
|
||||
|
||||
You will then simply need to confirm the transaction. It is a good opportunity to make sure everything is OK.
|
||||
|
||||
|
||||
|
||||
You should then receive your TFT on your Dashboard account within a few minutes.
|
||||
|
||||
You can see your TFT balance on the top of the screen. Here's an example of what it could look like:
|
||||
|
||||
|
||||
|
||||
> Note: You might need to refresh (reload) the webpage to see the new TFT added to the account.
|
||||
|
||||
That's it! You've swapped TFT from Stellar Chain to TFChain.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
@@ -1,94 +0,0 @@
|
||||
<h1>TFT on Ethereum</h2>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [TFT Ethereum-Stellar Bridge](#tft-ethereum-stellar-bridge)
|
||||
- [TFT and Metamask](#tft-and-metamask)
|
||||
- [Add TFT to Metamask](#add-tft-to-metamask)
|
||||
- [Buy TFT on Metamask](#buy-tft-on-metamask)
|
||||
- [Questions and Feedback](#questions-and-feedback)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
The TFT Stellar-Ethereum bridge serves as a vital link between the Stellar and Ethereum blockchains, enabling the seamless transfer of TFT tokens between these two networks. This bridge enhances interoperability and expands the utility of TFT by allowing users to leverage the strengths of both platforms. With the bridge in place, TFT holders can convert their tokens from the Stellar network to the Ethereum network and vice versa, unlocking new possibilities for engagement with decentralized applications, smart contracts, and the vibrant Ethereum ecosystem. This bridge promotes liquidity, facilitates cross-chain transactions, and encourages collaboration between the Stellar and Ethereum communities.
|
||||
|
||||
***
|
||||
|
||||
## TFT Ethereum-Stellar Bridge
|
||||
|
||||
The easiest way to transfer TFT between Ethereum and Stellar is to use the [TFT Ethereum Bridge](https://bridge.eth.threefold.io). We present here the main steps on how to use this bridge.
|
||||
|
||||
When you go to the [TFT Ethereum-Stellar bridge website](https://bridge.eth.threefold.io/), connect your Ethereum wallet. Then the bridge will present a QR code which you scan with your Stellar wallet. This will populate a transaction with the bridge wallet as the destination and an encoded form of your Ethereum address as the memo. The bridge will scan the transaction, decode the Ethereum wallet address, and deliver newly minted TFT on Ethereum, minus the bridge fees.
|
||||
|
||||
For the reverse operation, going from Ethereum to Stellar, there is a smart contract interaction that burns TFT on Ethereum while embedding your Stellar wallet address. The bridge will scan that transaction and release TFT from its vault wallet to the specified Stellar address, again minus the bridge fees.
|
||||
|
||||
Note that the contract address for TFT on Ethereum is the following: `0x395E925834996e558bdeC77CD648435d620AfB5b`.
|
||||
|
||||
To see the ThreeFold Token on Etherscan, check [this link](https://etherscan.io/token/0x395E925834996e558bdeC77CD648435d620AfB5b).
|
||||
|
||||
***
|
||||
|
||||
## TFT and Metamask
|
||||
|
||||
The ThreeFold Token (TFT) is available on Ethereum.
|
||||
It is implemented as a wrapped asset with the following token address:
|
||||
|
||||
```
|
||||
0x395E925834996e558bdeC77CD648435d620AfB5b
|
||||
```
|
||||
|
||||
We present here the basic steps to add TFT to Metamask. We also show how to buy TFT Metamask. Finally, we present the simple steps to use the [TFT Ethereum Bridge](https://bridge.eth.threefold.io/).
|
||||
|
||||
|
||||
***
|
||||
|
||||
### Add TFT to Metamask
|
||||
|
||||
Open Metamask and import the ThreeFold Token. First click on `import tokens`:
|
||||
|
||||
|
||||
|
||||
Then, choose `Custom Token`:
|
||||
|
||||
|
||||
|
||||
To add the ThreeFold Token, paste its Ethereum address in the field `Token contract address field`. The address is the following:
|
||||
|
||||
```
|
||||
0x395E925834996e558bdeC77CD648435d620AfB5b
|
||||
```
|
||||
|
||||
Once you paste the TFT contract address, the parameter `Token symbol` should automatically be filled with `TFT`.
|
||||
|
||||
Click on the button `Add Custom Token`.
|
||||
|
||||
|
||||
|
||||
To confirm, click on the button `Import tokens`:
|
||||
|
||||
|
||||
|
||||
TFT is now added to Metamask.
|
||||
|
||||
***
|
||||
|
||||
### Buy TFT on Metamask
|
||||
|
||||
Liquidity is present on Ethereum so you can use the "Swap" functionality from Metamask directly or go to [Uniswap](https://app.uniswap.org/#/swap) to swap Ethereum, or any other token, to TFT.
|
||||
|
||||
When using Uniswap, paste the TFT token address in the field `Select a token` to select TFT on Ethereum. The TFT token address is the following:
|
||||
|
||||
```
|
||||
0x395E925834996e558bdeC77CD648435d620AfB5b
|
||||
```
|
||||
|
||||
|
||||
|
||||
***
|
||||
|
||||
## Questions and Feedback
|
||||
|
||||
If you have any question, feel free to write a post on the [Threefold Forum](https://forum.threefold.io/).
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 216 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 89 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 178 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 263 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 108 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 136 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 154 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 245 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 179 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 165 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 37 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 119 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 109 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 79 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 155 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 112 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 225 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 157 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 126 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 21 KiB |
@@ -1,216 +0,0 @@
|
||||
<h1>Threefold Token: Buy TFT on Lobstr</h1>
|
||||
|
||||
<div class="youtubeVideoWrapper">
|
||||
<iframe title="How to Buy TFT on Lobstr" width="560" height="315" src="https://www.youtube-nocookie.com/embed/1N15bKztiqk" frameborder="0" allowfullscreen="" sandbox="allow-same-origin allow-scripts allow-popups"></iframe>
|
||||
</div>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Download the App and Create an Account](#download-the-app-and-create-an-account)
|
||||
- [Connect Your TF Connect App Wallet](#connect-your-tf-connect-app-wallet)
|
||||
- [Buy XLM with Fiat Currency](#buy-xlm-with-fiat-currency)
|
||||
- [Swap XLM for TFT](#swap-xlm-for-tft)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
The Threefold token (TFT) is the utility token of the Threefold Grid, a decentralized and open-source project offering network, compute and storage capacity.
|
||||
|
||||
Threefold Tokens (TFT) are created (minted) by the ThreeFold Blockchain (TFChain) only when new Internet capacity is added to the ThreeFold Grid by farmers. For this reason, TFT is a pure utility token as minting is solely the result of farming on the Threefold Grid.
|
||||
|
||||
* To **farm** TFT, read the [complete farming guide](https://forum.threefold.io/t/threefold-farming-guide-part-1/2989).
|
||||
|
||||
* To **buy** TFT, follow this guide.
|
||||
|
||||
There are many ways to buy TFT:
|
||||
|
||||
* You can buy TFT on [Lobstr](https://lobstr.co/)
|
||||
|
||||
* You can buy TFT at [GetTFT.com](https://gettft.com/gettft/)
|
||||
|
||||
* You can buy TFT on [Pancake Swap](https://pancakeswap.finance/swap?inputCurrency=BNB&outputCurrency=0x8f0FB159380176D324542b3a7933F0C2Fd0c2bbf)
|
||||
|
||||
For the current guide, we will show how to buy TFT on the [Lobstr app](https://lobstr.co/).
|
||||
The process is simple.
|
||||
|
||||
Note that it is possible to do these steps without connecting the Lobstr wallet to the TF Connect App wallet. But doing this has a clear advantage: when we buy and swap on Lobstr, the TFT is directly accessible on the TF Connect app wallet.
|
||||
|
||||
Here we go!
|
||||
|
||||
***
|
||||
|
||||
## Download the App and Create an Account
|
||||
|
||||
Go on [www.lobstr.co](https://www.lobstr.co) and download the Lobstr app.
|
||||
You can download it for Android or iOS.
|
||||
|
||||
|
||||
|
||||
We will show here the steps for Android, but it is very similar with iOS.
|
||||
Once you've clicked on the Android button, you can click install on the Google Store page:
|
||||
|
||||
|
||||
|
||||
Once the app is downloaded, open it:
|
||||
|
||||
|
||||
|
||||
On the Lobstr app, click on **Create Account**:
|
||||
|
||||
|
||||
|
||||
You will then need to enter your email address:
|
||||
|
||||
|
||||
|
||||
Then, choose a safe password for your account:
|
||||
|
||||
|
||||
|
||||
Once this is done, you will need to verify your email.
|
||||
|
||||
Click on **Verify Email** and then go check your email inbox.
|
||||
|
||||
|
||||
|
||||
Simply click on **Verify Email** on the email you've received.
|
||||
|
||||
|
||||
|
||||
Once your email is verified, you can sign in to your Lobstr account:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
***
|
||||
|
||||
## Connect Your TF Connect App Wallet
|
||||
|
||||
You will then need to either create a new wallet or connect an existing wallet.
|
||||
|
||||
Since we are working on the Threefold ecosystem, it is very easy and practical to simply connect your Threefold Connect app wallet. You can also create a new wallet.
|
||||
|
||||
Using the TF Connect wallet is very useful and quick. When you buy XLM and swap XLM tokens for TFTs, they will be directly available on your TF Connect app wallet.
|
||||
|
||||
|
||||
|
||||
To connect your TF Connect app wallet, you will need to find your Stellar address and chain secret key.
|
||||
This is very simple to do.
|
||||
|
||||
Click on **I have a public or secret key**.
|
||||
|
||||
|
||||
|
||||
As you can see on this next picture, you need the Stellar address and secret key to properly connect your TF Connect app wallet to Lobstr:
|
||||
|
||||
|
||||
|
||||
To find your Stellar address and secret key, go on the TF Connect app and select the **Wallet** section:
|
||||
|
||||
|
||||
|
||||
At the top of the section, click on the **copy** button to copy your Stellar Address:
|
||||
|
||||
|
||||
|
||||
Now, we will find the Stellar secret key.
|
||||
At the botton of the section, click on the encircled **i** button:
|
||||
|
||||
|
||||
|
||||
Next, click on the **eye** button to reveal your secret key:
|
||||
|
||||
|
||||
|
||||
You can now simply click on the **copy** button on the right:
|
||||
|
||||
|
||||
|
||||
That's it! You've now connected your TF Connect app wallet to your Lobstr account.
|
||||
|
||||
## Buy XLM with Fiat Currency
|
||||
|
||||
Now, all we need to do, is buy XLM and then swap it for TFT.
|
||||
It will be directly available in your TF Connect App wallet.
|
||||
|
||||
On the Lobstr app, click on the top right menu button:
|
||||
|
||||
|
||||
|
||||
Then, click on **Buy Crypto**:
|
||||
|
||||
|
||||
|
||||
By default, the crypto selected is XLM. This is alright for us as we will quickly swap the XLM for TFT.
|
||||
|
||||
On the Buy Crypto page, you can choose the type of Fiat currency you want.
|
||||
By default it is in USD. To select some othe fiat currency, you can click on **ALL** and see the available fiat currencies:
|
||||
|
||||
|
||||
|
||||
You can search or select the current you want for the transfer:
|
||||
|
||||
|
||||
|
||||
You will then need to decide how much XLM you want to buy. Note that there can be a minimum amount.
|
||||
Once you chose the desired amount, click on **Continue**.
|
||||
|
||||
|
||||
|
||||
Lobstr will then ask you to proceed to a payment method. In this case, it is Moonpay.
|
||||
Note that in some cases, your credit card won't accept Moonpay payments. You will simply need to confirm with them that you agree with transacting with Moonpay. This can be done by phone. Check with your bank and credit card company if this applies.
|
||||
|
||||
|
||||
|
||||
Once you've set up your Moonpay payment method, you will need to process and confirm the transaction:
|
||||
|
||||
|
||||
|
||||
|
||||
You will then see a processing window.
|
||||
This process is usually fast. Within a few minutes, you should receive your XLM.
|
||||
|
||||
|
||||
|
||||
Once the XLM is delivered, you will receive a notification:
|
||||
|
||||
|
||||
|
||||
When your transaction is complete, you will see this message:
|
||||
|
||||
|
||||
|
||||
On the Trade History page, you can choose to download the csv file version of your transaction:
|
||||
|
||||
|
||||
|
||||
That's it! You've bought XLM on Lobstr and Moonpay.
|
||||
|
||||
## Swap XLM for TFT
|
||||
|
||||
Now we want to swap the XLM tokens for the Threefold tokens (TFT).
|
||||
This is even easier than the previous steps.
|
||||
|
||||
Go to the Lobstr Home menu and select **Swap**:
|
||||
|
||||
|
||||
|
||||
On the **Swap** page, write "tft" and select the Threefold token:
|
||||
|
||||
|
||||
|
||||
Select the amount of XLM you want to swap. It is recommended to keep at least 1 XLM in your wallet for transaction fees.
|
||||
|
||||
|
||||
|
||||
Within a few seconds, you will receive a confirmation that your swap is completed:
|
||||
Note that the TFT is directly sent on your TF Connect app wallet.
|
||||
|
||||
|
||||
|
||||
That's it. You've swapped XLM for TFT.
|
||||
|
||||
You can now use your TFT to deploy workloads on the Threefold Grid.
|
||||
@@ -1,6 +0,0 @@
|
||||
<h1> ThreeFold Token </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [TFT on Lobstr](../TF_Token/tft_lobstr/tft_lobstr.html)
|
||||
- [TFT on Ethereum](../TF_Token/tft_ethereum/tft_ethereum.html)
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 330 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 154 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 223 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 273 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 206 KiB |
@@ -1,229 +0,0 @@
|
||||
|
||||
<h1> Planetary Network </h1>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Install](#install)
|
||||
- [Run](#run)
|
||||
- [Linux](#linux)
|
||||
- [MacOS](#macos)
|
||||
- [Test Connectivity](#test-connectivity)
|
||||
- [Firewalls](#firewalls)
|
||||
- [Linux](#linux-1)
|
||||
- [MacOS](#macos-1)
|
||||
- [Get Yggdrasil IP](#get-yggdrasil-ip)
|
||||
- [Add Peers](#add-peers)
|
||||
- [Clients](#clients)
|
||||
- [Peers](#peers)
|
||||
- [Central europe](#central-europe)
|
||||
- [Ghent](#ghent)
|
||||
- [Austria](#austria)
|
||||
- [Peers config for usage in every Yggdrasil - Planetary Network client](#peers-config-for-usage-in-every-yggdrasil---planetary-network-client)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In a first phase, to get started, you need to launch the planetary network by running [Yggdrasil](https://yggdrasil-network.github.io) from the command line.
|
||||
|
||||
Yggdrasil is an implementation of a fully end-to-end encrypted IPv6 network. It is lightweight, self-arranging, supported on multiple platforms, and allows pretty much any IPv6-capable application to communicate securely with other nodes on the network. Yggdrasil does not require you to have IPv6 Internet connectivity - it also works over IPv4.
|
||||
|
||||
## Install
|
||||
|
||||
Yggdrasil is necessary for communication between your local machine and the nodes on the Grid that you deploy to. Binaries and packages are available for all major operating systems, or it can be built from source. Find installation instructions here.
|
||||
|
||||
After installation, you'll need to add at least one publicly available peer to your Yggdrasil configuration file. By default on Unix based systems, you'll find the file at `/etc/yggdrasil.conf`. To find peers, check this site, which compiles and displays the peer information available on Github.
|
||||
|
||||
Add peers to your configuration file like so:
|
||||
|
||||
```
|
||||
Peers: ["PEER_URL:PORT", "PEER_URL:PORT", ...]
|
||||
```
|
||||
|
||||
Please consult [yggdrasil installation page](https://yggdrasil-network.github.io/installation.html) for more information and clients
|
||||
|
||||
## Run
|
||||
|
||||
### Linux
|
||||
|
||||
On Linux with `systemd`, Yggdrasil can be started and enabled as a service, or run manually from the command line:
|
||||
|
||||
```
|
||||
sudo yggdrasil -useconffile /etc/yggdrasil.conf
|
||||
```
|
||||
|
||||
Get your IPv6 address with following command :
|
||||
|
||||
```
|
||||
yggdrasilctl getSelf
|
||||
```
|
||||
|
||||
### MacOS
|
||||
|
||||
The MacOS package will automatically install and start the `launchd` service. After adding peers to your config file, restart Yggdrasil by stopping the service (it will be restarted automatically):
|
||||
|
||||
```
|
||||
sudo launchctl stop yggdrasil
|
||||
```
|
||||
|
||||
Get your IPv6 address with following command :
|
||||
|
||||
```
|
||||
sudo yggdrasilctl getSelf
|
||||
```
|
||||
|
||||
## Test Connectivity
|
||||
|
||||
To ensure that you have successfully connected to the Yggdrasil network, try loading the site in your browser:
|
||||
|
||||
```
|
||||
http://[319:3cf0:dd1d:47b9:20c:29ff:fe2c:39be]/
|
||||
```
|
||||
|
||||
## Firewalls
|
||||
|
||||
Creating deployments on the Grid also requires that nodes can reach your machine as well. This means that a local firewall preventing inbound connections will cause deployments to fail.
|
||||
|
||||
### Linux
|
||||
|
||||
On systems using `iptables`, check:
|
||||
```
|
||||
sudo ip6tables -S INPUT
|
||||
```
|
||||
|
||||
If the first line is `-P INPUT DROP`, then all inbound connections over IPv6 will be blocked. To open inbound connections, run:
|
||||
|
||||
```
|
||||
sudo ip6tables -P INPUT ACCEPT
|
||||
```
|
||||
|
||||
To make this persist after a reboot, run:
|
||||
|
||||
```
|
||||
sudo ip6tables-save
|
||||
```
|
||||
|
||||
If you'd rather close the firewall again after you're done, use:
|
||||
|
||||
```
|
||||
sudo ip6tables -P INPUT DROP
|
||||
```
|
||||
|
||||
### MacOS
|
||||
|
||||
The MacOS system firewall is disabled by default. You can check your firewall settings according to instructions here.
|
||||
|
||||
## Get Yggdrasil IP
|
||||
|
||||
Once Yggdrasil is installed, you can find your Yggdrasil IP address using this command on both Linux and Mac:
|
||||
|
||||
```
|
||||
yggdrasil -useconffile /etc/yggdrasil.conf -address
|
||||
```
|
||||
|
||||
You'll need this address when registering your twin on TFChain later.
|
||||
|
||||
|
||||
## Add Peers
|
||||
|
||||
|
||||
- Add the needed [peers](https://publicpeers.neilalexander.dev/) in the config file generated under Peers.
|
||||
|
||||
**example**:
|
||||
```
|
||||
Peers:
|
||||
[
|
||||
tls://54.37.137.221:11129
|
||||
]
|
||||
```
|
||||
- Restart yggdrasil by
|
||||
|
||||
systemctl restart yggdrasil
|
||||
|
||||
## Clients
|
||||
|
||||
- [planetary network connector](https://github.com/threefoldtech/planetary_network)
|
||||
|
||||
## Peers
|
||||
|
||||
### Central europe
|
||||
|
||||
#### Ghent
|
||||
|
||||
- tcp://gent01.grid.tf:9943
|
||||
- tcp://gent02.grid.tf:9943
|
||||
- tcp://gent03.grid.tf:9943
|
||||
- tcp://gent04.grid.tf:9943
|
||||
- tcp://gent01.test.grid.tf:9943
|
||||
- tcp://gent02.test.grid.tf:9943
|
||||
- tcp://gent01.dev.grid.tf:9943
|
||||
- tcp://gent02.dev.grid.tf:9943
|
||||
|
||||
### Austria
|
||||
|
||||
- tcp://gw291.vienna1.greenedgecloud.com:9943
|
||||
- tcp://gw293.vienna1.greenedgecloud.com:9943
|
||||
- tcp://gw294.vienna1.greenedgecloud.com:9943
|
||||
- tcp://gw297.vienna1.greenedgecloud.com:9943
|
||||
- tcp://gw298.vienna1.greenedgecloud.com:9943
|
||||
- tcp://gw299.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw300.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw304.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw306.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw307.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw309.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw313.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw324.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw326.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw327.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw328.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw330.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw331.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw333.salzburg1.greenedgecloud.com:9943
|
||||
- tcp://gw422.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw423.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw424.vienna2.greenedgecloud.com:9943
|
||||
- tcp://gw425.vienna2.greenedgecloud.com:9943
|
||||
|
||||
## Peers config for usage in every Yggdrasil - Planetary Network client
|
||||
|
||||
```
|
||||
Peers:
|
||||
[
|
||||
# Threefold Lochrist
|
||||
tcp://gent01.grid.tf:9943
|
||||
tcp://gent02.grid.tf:9943
|
||||
tcp://gent03.grid.tf:9943
|
||||
tcp://gent04.grid.tf:9943
|
||||
tcp://gent01.test.grid.tf:9943
|
||||
tcp://gent02.test.grid.tf:9943
|
||||
tcp://gent01.dev.grid.tf:9943
|
||||
tcp://gent02.dev.grid.tf:9943
|
||||
# GreenEdge
|
||||
tcp://gw291.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw293.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw294.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw297.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw298.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw299.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw300.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw304.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw306.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw307.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw309.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw313.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw324.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw326.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw327.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw328.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw330.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw331.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw333.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw422.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw423.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw424.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw425.vienna2.greenedgecloud.com:9943
|
||||
]
|
||||
```
|
||||
|
||||
@@ -1,186 +0,0 @@
|
||||
<h1> Deploy a Full VM and Run Cockpit, a Web-based Interface for Servers </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Deploy a Full VM and Create a Root-Access User](#deploy-a-full-vm-and-create-a-root-access-user)
|
||||
- [Set the VM and Install Cockpit](#set-the-vm-and-install-cockpit)
|
||||
- [Change the Network System Daemon](#change-the-network-system-daemon)
|
||||
- [Set a Firewall](#set-a-firewall)
|
||||
- [Access Cockpit](#access-cockpit)
|
||||
- [Conclusion](#conclusion)
|
||||
- [Acknowledgements and References](#acknowledgements-and-references)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this Threefold Guide, we show how easy it is to deploy a full VM and access Cockpit, a web-based interface to manage servers. For more information on Cockpit, visit this [link](https://cockpit-project.org/).
|
||||
|
||||
For more information on deploying a full VM and using SSH remote connection, read [this SSH guide](../../ssh_guide/ssh_guide.md).
|
||||
|
||||
If you are new to the Threefold ecosystem and you want to deploy workloads on the Threefold Grid, read the [Get Started section](../../tfgrid3_getstarted.md) of the Threefold Manual.
|
||||
|
||||
Note that the two sections [Change the Network System Daemon](#change-the-network-system-daemon) and [Set a Firewall](#set-a-firewall) are optional. That being said, they provide more features and security to the deployment.
|
||||
|
||||
|
||||
|
||||
## Deploy a Full VM and Create a Root-Access User
|
||||
|
||||
To start, you must [deploy and SSH into a full VM](../../ssh_guide/ssh_guide.md).
|
||||
|
||||
* Go to the [Threefold dashboard](https://dashboard.grid.tf/#/)
|
||||
* Deploy a full VM (e.g. Ubuntu 22.04)
|
||||
* With an IPv4 Address
|
||||
* After deployment, copy the IPv4 address
|
||||
* Connect into the VM via SSH
|
||||
* ```
|
||||
ssh root@VM_IPv4_address
|
||||
```
|
||||
* Create a new user with root access
|
||||
* Here we use `newuser` as an example
|
||||
* ```
|
||||
adduser newuser
|
||||
```
|
||||
* To see the directory of the new user
|
||||
* ```
|
||||
ls /home
|
||||
```
|
||||
* Give sudo capacity to the new user
|
||||
* ```
|
||||
usermod -aG sudo newuser
|
||||
```
|
||||
* Make the new user accessible by SSH
|
||||
* ```
|
||||
su - newuser
|
||||
```
|
||||
* ```
|
||||
mkdir ~/.ssh
|
||||
```
|
||||
* ```
|
||||
nano ~/.ssh/authorized_keys
|
||||
```
|
||||
* add the authorized public key in the file, then save and quit
|
||||
* Exit the VM and reconnect with the new user
|
||||
* ```
|
||||
exit
|
||||
```
|
||||
* ```
|
||||
ssh newuser@VM_IPv4_address
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Set the VM and Install Cockpit
|
||||
|
||||
* Update and upgrade the VM
|
||||
* ```
|
||||
sudo apt update -y && sudo apt upgrade -y && sudo apt-get update -y
|
||||
```
|
||||
* Install Cockpit
|
||||
* ```
|
||||
. /etc/os-release && sudo apt install -t ${UBUNTU_CODENAME}-backports cockpit -y
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Change the Network System Daemon
|
||||
|
||||
We now change the system daemon that manages network configurations. We will be using [NetworkManager](https://networkmanager.dev/) instead of [networkd](https://wiki.archlinux.org/title/systemd-networkd). This will give us further possibilities on Cockpit.
|
||||
|
||||
* Install NetworkManager. Note that it might already be installed.
|
||||
* ```
|
||||
sudo apt install network-manager -y
|
||||
```
|
||||
* Update the `.yaml` file
|
||||
* Go to netplan's directory
|
||||
* ```
|
||||
cd /etc/netplan
|
||||
```
|
||||
* Search for the proper `.yaml` file name
|
||||
* ```
|
||||
ls -l
|
||||
```
|
||||
* Update the `.yaml` file
|
||||
* ```
|
||||
sudo nano 50-cloud-init.yaml
|
||||
```
|
||||
* Add the following lines under `network:`
|
||||
* ```
|
||||
version: 2
|
||||
renderer: NetworkManager
|
||||
```
|
||||
* Note that these two lines should be aligned with `ethernets:`
|
||||
* Remove `version: 2` at the bottom of the file
|
||||
* Save and exit the file
|
||||
* Disable networkd and enable NetworkManager
|
||||
* ```
|
||||
sudo systemctl disable systemd-networkd
|
||||
```
|
||||
* ```
|
||||
sudo systemctl enable NetworkManager
|
||||
```
|
||||
* Apply netplan to set NetworkManager
|
||||
* ```
|
||||
sudo netplan apply
|
||||
```
|
||||
* Reboot the system to load the new kernel and to properly set NetworkManager
|
||||
* ```
|
||||
sudo reboot
|
||||
```
|
||||
* Reconnect to the VM
|
||||
* ```
|
||||
ssh newuser@VM_IPv4_address
|
||||
```
|
||||
|
||||
|
||||
## Set a Firewall
|
||||
|
||||
We now set a firewall. We note that [ufw](https://wiki.ubuntu.com/UncomplicatedFirewall) is not compatible with Cockpit and for this reason, we will be using [firewalld](https://firewalld.org/).
|
||||
|
||||
* Install firewalld
|
||||
* ```
|
||||
sudo apt install firewalld -y
|
||||
```
|
||||
|
||||
* Add Cockpit to firewalld
|
||||
* ```
|
||||
sudo firewall-cmd --add-service=cockpit
|
||||
```
|
||||
* ```
|
||||
sudo firewall-cmd --add-service=cockpit --permanent
|
||||
```
|
||||
* See if Cockpit is available
|
||||
* ```
|
||||
sudo firewall-cmd --info-service=cockpit
|
||||
```
|
||||
|
||||
* See the status of firewalld
|
||||
* ```
|
||||
sudo firewall-cmd --state
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Access Cockpit
|
||||
|
||||
* On your web browser, write the following URL with the proper VM IPv4 address
|
||||
* ```
|
||||
VM_IPv4_Address:9090
|
||||
```
|
||||
* Enter the username and password of the root-access user
|
||||
* You might need to grant administrative access to the user
|
||||
* On the top right of the Cockpit window, click on `Limited access`
|
||||
* Enter the root-access user password then click `Authenticate`
|
||||
|
||||
|
||||
|
||||
## Conclusion
|
||||
|
||||
You now have access to a web-based graphical interface to manage your VM. You can read [Cockpit's documentation](https://cockpit-project.org/documentation.html) to explore further this interface.
|
||||
|
||||
|
||||
|
||||
## Acknowledgements and References
|
||||
|
||||
A big thank you to Drew Smith for his [advice on using NetworkManager](https://forum.threefold.io/t/cockpit-managed-ubuntu-vm/3376) instead of networkd with Cockpit.
|
||||
@@ -1,184 +0,0 @@
|
||||
<h1> Deploy a Full VM and Run Apache Guacamole (RDP Connection, Remote Desktop) </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Deploy a Full VM and Create a Root-Access User](#deploy-a-full-vm-and-create-a-root-access-user)
|
||||
- [SSH with Root-Access User, Install Prerequisites and Apache Guacamole](#ssh-with-root-access-user-install-prerequisites-and-apache-guacamole)
|
||||
- [Access Apache Guacamole and Create Admin-Access User](#access-apache-guacamole-and-create-admin-access-user)
|
||||
- [Download the Desktop Environment and Run xrdp](#download-the-desktop-environment-and-run-xrdp)
|
||||
- [Create an RDP Connection and Access the Server Remotely](#create-an-rdp-connection-and-access-the-server-remotely)
|
||||
- [Feedback and Questions](#feedback-and-questions)
|
||||
- [References](#references)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this guide, we deploy a full virtual machine (Ubuntu 20.04) on the Threefold Grid with IPv4. We install and run [Apache Guacamole](https://guacamole.apache.org/) and access the VM with remote desktop connection by using [xrdp](https://www.xrdp.org/).
|
||||
|
||||
The Apache Guacamole instance has a two-factor authorization to give further security to the deployment.
|
||||
|
||||
With Apache Guacamole, a user can access different deployments and command servers remotely, with desktop access.
|
||||
|
||||
This guide can be done on a Windows, MAC, or Linux computer. For more information on deploying a full VM and using SSH remote connection, read this [SSH guide](../../ssh_guide/ssh_guide.md).
|
||||
|
||||
If you are new to the Threefold ecosystem and you want to deploy workloads on the Threefold Grid, read the [Get Started section](../../tfgrid3_getstarted.md) of the Threefold Manual.
|
||||
|
||||
|
||||
|
||||
## Deploy a Full VM and Create a Root-Access User
|
||||
|
||||
* Go to the [Threefold Dashboard](https://dashboard.grid.tf/#/)
|
||||
* Deploy a full VM (Ubuntu 20.04) with at least the minimum specs for a desktop environment
|
||||
* IPv4 Address
|
||||
* Minimum vcores: 2vcores
|
||||
* Minimum Gb of RAM: 4Gb
|
||||
* Minimum storage: 15Gb
|
||||
* After deployment, note the VM IPv4 address
|
||||
* Connect to the VM via SSH
|
||||
* ```
|
||||
ssh root@VM_IPv4_address
|
||||
```
|
||||
* Once connected, create a new user with root access (for this guide we use "newuser")
|
||||
* ```
|
||||
adduser newuser
|
||||
```
|
||||
* You should now see the new user directory
|
||||
* ```
|
||||
ls /home
|
||||
```
|
||||
* Give sudo capacity to the new user
|
||||
* ```
|
||||
usermod -aG sudo newuser
|
||||
```
|
||||
* Make the new user accessible by SSH
|
||||
* ```
|
||||
su - newuser
|
||||
```
|
||||
* ```
|
||||
mkdir ~/.ssh
|
||||
```
|
||||
* Add authorized public key in the file and save it
|
||||
* ```
|
||||
nano ~/.ssh/authorized_keys
|
||||
```
|
||||
* Exit the VM and reconnect with the new user
|
||||
|
||||
|
||||
|
||||
## SSH with Root-Access User, Install Prerequisites and Apache Guacamole
|
||||
|
||||
* SSH into the VM
|
||||
* ```
|
||||
ssh newuser@VM_IPv4_address
|
||||
```
|
||||
* Update and upgrade Ubuntu
|
||||
* ```
|
||||
sudo apt update && sudo apt upgrade -y && sudo apt-get install software-properties-common -y
|
||||
```
|
||||
* Download and run Apache Guacamole
|
||||
* ```
|
||||
wget -O guac-install.sh https://git.io/fxZq5
|
||||
```
|
||||
* ```
|
||||
chmod +x guac-install.sh
|
||||
```
|
||||
* ```
|
||||
sudo ./guac-install.sh
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Access Apache Guacamole and Create Admin-Access User
|
||||
|
||||
* On your local computer, open a browser and write the following URL with the proper IPv4 address
|
||||
* ```
|
||||
https://VM_IPv4_address:8080/guacamole
|
||||
```
|
||||
* On Guacamole, enter the following for both the username and the password
|
||||
* ```
|
||||
guacadmin
|
||||
```
|
||||
* Download the [TOTP](https://totp.app/) app on your Android or iOS
|
||||
* Scan the QR Code
|
||||
* Enter the code
|
||||
* Next time you log in
|
||||
* go to the TOTP app and enter the given code
|
||||
* Go to the Guacamole Settings
|
||||
* Users
|
||||
* Create a new user with all admin privileges
|
||||
* Log out of the session
|
||||
* Enter with the new admin user
|
||||
* Go to Settings
|
||||
* Users
|
||||
* Delete the default user
|
||||
* Apache Guacamole is now installed
|
||||
|
||||
|
||||
|
||||
## Download the Desktop Environment and Run xrdp
|
||||
|
||||
* Download a Ubuntu desktop environment on the VM
|
||||
* ```
|
||||
sudo apt install tasksel -y && sudo apt install lightdm -y
|
||||
```
|
||||
* Choose lightdm
|
||||
* Run tasksel and choose `ubuntu desktop`
|
||||
* ```
|
||||
sudo tasksel
|
||||
```
|
||||
|
||||
* Download and run xrdp
|
||||
* ```
|
||||
wget https://c-nergy.be/downloads/xRDP/xrdp-installer-1.4.6.zip
|
||||
```
|
||||
* ```
|
||||
unzip xrdp-installer-1.4.6.zip
|
||||
```
|
||||
* ```
|
||||
bash xrdp-installer-1.4.6.sh
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Create an RDP Connection and Access the Server Remotely
|
||||
|
||||
* Create an RDP connection on Guacamole
|
||||
* Open Guacamole
|
||||
* ```
|
||||
http://VM_IPv4_address:8080/guacamole/
|
||||
```
|
||||
* Go to Settings
|
||||
* Click on Connections
|
||||
* Click on New Connection
|
||||
* Write the following parameters
|
||||
* Name: Choose a name for the connection
|
||||
* Location: ROOT
|
||||
* Protocol: RDP
|
||||
* Network
|
||||
* Hostname: VM_IPv4_Address
|
||||
* Port: 3389
|
||||
* Authentication
|
||||
* Username: your root-access username (newuser)
|
||||
* Password: your root-access username password (newuser)
|
||||
* Security mode: Any
|
||||
* Ignore server certificate: Yes
|
||||
* Click Save
|
||||
* Go to the Apache Guacamole Home menu (top right button)
|
||||
* Click on the new connection
|
||||
* The remote desktop access is done
|
||||
|
||||
|
||||
|
||||
## Feedback and Questions
|
||||
|
||||
If you have any questions, let us know by writing a post on the [Threefold Forum](https://forum.threefold.io/).
|
||||
|
||||
|
||||
|
||||
## References
|
||||
|
||||
Apache Guacamole for Secure Remote Access to your Computers, [https://discussion.scottibyte.com/t/apache-guacamole-for-secure-remote-access-to-your-computers/32](https://discussion.scottibyte.com/t/apache-guacamole-for-secure-remote-access-to-your-computers/32)
|
||||
|
||||
MysticRyuujin's guac-install, [https://github.com/MysticRyuujin/guac-install](https://github.com/MysticRyuujin/guac-install)
|
||||
@@ -1,11 +0,0 @@
|
||||
# Remote Desktop and GUI
|
||||
|
||||
This section of the Threefold Guide provides different methods to access your 3node servers with either a remote desktop protocol or a graphical user interface (GUI).
|
||||
|
||||
If you have any questions, or if you would like to see a specific guide on remote desktop connection or GUI, please let us know by writing a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Cockpit: a Web-based Graphical Interface for Servers](./cockpit_guide/cockpit_guide.md)
|
||||
- [XRDP: an Open-Source Remote Desktop Procol](./xrdp_guide/xrdp_guide.md)
|
||||
- [Apache Guacamole: a Clientless Remote Desktop Gateway.](./guacamole_guide/guacamole_guide.md)
|
||||
@@ -1,168 +0,0 @@
|
||||
<h1> Deploy a Full VM and Run XRDP for Remote Desktop Connection </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Server Side: Deploy the Full VM, install a desktop and XRDP](#server-side-deploy-the-full-vm-install-a-desktop-and-xrdp)
|
||||
- [Client Side: Install Remote Desktop Connection for Windows, MAC or Linux](#client-side-install-remote-desktop-connection-for-windows-mac-or-linux)
|
||||
- [Download the App](#download-the-app)
|
||||
- [Connect Remotely](#connect-remotely)
|
||||
- [Conclusion](#conclusion)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this guide, we learn how to deploy a full virtual machine on a 3node on the Threefold Grid.
|
||||
We access Ubuntu with a desktop environment to offer a graphical user interface (GUI).
|
||||
|
||||
This guide can be done on a Windows, MAC, or Linux computer. The only difference will be in the Remote Desktop app. The steps are very similar.
|
||||
|
||||
For more information on deploying a full VM and using SSH remote connection, read this [SSH guide](../../ssh_guide/ssh_guide.md).
|
||||
|
||||
If you are new to the Threefold ecosystem and you want to deploy workloads on the Threefold Grid, read the [Get Started section](../../tfgrid3_getstarted.md) of the Threefold Manual.
|
||||
|
||||
|
||||
|
||||
## Server Side: Deploy the Full VM, install a desktop and XRDP
|
||||
|
||||
* Go to the [Threefold Dashboard](https://dashboard.grid.tf/#/)
|
||||
* Deploy a full VM (Ubuntu 20.04)
|
||||
* With an IPv4 Address
|
||||
* After deployment, copy the IPv4 address
|
||||
* To SSH into the VM, write in the terminal
|
||||
* ```
|
||||
ssh root@VM_IPv4_address
|
||||
```
|
||||
* Once connected, update, upgrade and install the desktop environment
|
||||
* Update
|
||||
* ```
|
||||
sudo apt update -y && sudo apt upgrade -y
|
||||
```
|
||||
* Install a light-weight desktop environment (Xfce)
|
||||
* ```
|
||||
sudo apt install xfce4 xfce4-goodies -y
|
||||
```
|
||||
* Create a user with root access
|
||||
* ```
|
||||
adduser newuser
|
||||
```
|
||||
* ```
|
||||
ls /home
|
||||
```
|
||||
* You should see the newuser directory
|
||||
* Give sudo capacity to newuser
|
||||
* ```
|
||||
usermod -aG sudo newuser
|
||||
```
|
||||
* Make newuser accessible by SSH
|
||||
* ```
|
||||
su - newuser
|
||||
```
|
||||
* ```
|
||||
mkdir ~/.ssh
|
||||
```
|
||||
* ```
|
||||
nano ~/.ssh/authorized_keys
|
||||
```
|
||||
* add authorized public key in file and save
|
||||
* Exit the VM and reconnect with new user
|
||||
* ```
|
||||
exit
|
||||
```
|
||||
* Reconnect to the VM terminal and install XRDP
|
||||
* ```
|
||||
ssh newuser@VM_IPv4_address
|
||||
```
|
||||
* Install XRDP
|
||||
* ```
|
||||
sudo apt install xrdp -y
|
||||
```
|
||||
* Check XRDP status
|
||||
* ```
|
||||
sudo systemctl status xrdp
|
||||
```
|
||||
* If not running, run manually:
|
||||
* ```
|
||||
sudo systemctl start xrdp
|
||||
```
|
||||
* If needed, configure xrdp (optional)
|
||||
* ```
|
||||
sudo nano /etc/xrdp/xrdp.ini
|
||||
```
|
||||
* Create a session with root-access user
|
||||
Move to home directory
|
||||
* Go to home directory of root-access user
|
||||
* ```
|
||||
cd ~
|
||||
```
|
||||
* Create session
|
||||
* ```
|
||||
echo "xfce4-session" | tee .xsession
|
||||
```
|
||||
* Restart the server
|
||||
* ```
|
||||
sudo systemctl restart xrdp
|
||||
```
|
||||
|
||||
* Find your local computer IP address
|
||||
* On your local computer terminal, write
|
||||
* ```
|
||||
curl ifconfig.me
|
||||
```
|
||||
|
||||
* On the VM terminal, allow client computer port to the firewall (ufw)
|
||||
* ```
|
||||
sudo ufw allow from your_local_ip/32 to any port 3389
|
||||
```
|
||||
* Allow SSH connection to your firewall
|
||||
* ```
|
||||
sudo ufw allow ssh
|
||||
```
|
||||
* Verify status of the firewall
|
||||
* ```
|
||||
sudo ufw status
|
||||
```
|
||||
* If not active, do the following:
|
||||
* ```
|
||||
sudo ufw disable
|
||||
```
|
||||
* ```
|
||||
sudo ufw enable
|
||||
```
|
||||
* Then the ufw status should show changes
|
||||
* ```
|
||||
sudo ufw status
|
||||
```
|
||||
|
||||
|
||||
## Client Side: Install Remote Desktop Connection for Windows, MAC or Linux
|
||||
|
||||
For the client side (the local computer accessing the VM remotely), you can use remote desktop connection for Windows, MAC and Linux. The process is very similar in all three cases.
|
||||
|
||||
Simply download the app, open it and write the IPv4 address of the VM. You then will need to write the username and password to enter into your VM.
|
||||
|
||||
### Download the App
|
||||
|
||||
* Client side Remote app
|
||||
* Windows
|
||||
* [Remote Desktop Connection app](https://apps.microsoft.com/store/detail/microsoft-remote-desktop/9WZDNCRFJ3PS?hl=en-ca&gl=ca&rtc=1)
|
||||
* MAC
|
||||
* Download in app store
|
||||
* [Microsoft Remote Desktop Connection app](https://apps.apple.com/ca/app/microsoft-remote-desktop/id1295203466?mt=12)
|
||||
* Linux
|
||||
* [Remmina RDP Client](https://remmina.org/)
|
||||
|
||||
### Connect Remotely
|
||||
|
||||
* General process
|
||||
* In the Remote app, enter the following:
|
||||
* the IPv4 Address of the VM
|
||||
* the VM root-access username and password
|
||||
* You now have remote desktop connection to your VM
|
||||
|
||||
|
||||
|
||||
## Conclusion
|
||||
|
||||
You now have a remote access to the desktop environment of your VM. If you have any questions, let us know by writing a post on the [Threefold Forum](https://forum.threefold.io/).
|
||||
@@ -1,4 +0,0 @@
|
||||
- [**Manual Home**](@manual3_home_new)
|
||||
---------
|
||||
**Get Started**
|
||||
!!!include:getstarted_toc
|
||||
@@ -1,10 +0,0 @@
|
||||
<h1> SSH Remote Connection </h1>
|
||||
|
||||
SSH is a secure protocol used as the primary means of connecting to Linux servers remotely. It provides a text-based interface by spawning a remote shell. After connecting, all commands you type in your local terminal are sent to the remote server and executed there.
|
||||
|
||||
<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)
|
||||
@@ -1,297 +0,0 @@
|
||||
<h1> SSH Remote Connection with OpenSSH </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Main Steps and Prerequisites](#main-steps-and-prerequisites)
|
||||
- [Step-by-Step Process with OpenSSH](#step-by-step-process-with-openssh)
|
||||
- [Linux](#linux)
|
||||
- [SSH into a 3Node with IPv4 on Linux](#ssh-into-a-3node-with-ipv4-on-linux)
|
||||
- [SSH into a 3Node with the Planetary Network on Linux](#ssh-into-a-3node-with-the-planetary-network-on-linux)
|
||||
- [MAC](#mac)
|
||||
- [SSH into a 3Node with IPv4 on MAC](#ssh-into-a-3node-with-ipv4-on-mac)
|
||||
- [SSH into a 3Node with the Planetary Network on MAC](#ssh-into-a-3node-with-the-planetary-network-on-mac)
|
||||
- [Windows](#windows)
|
||||
- [SSH into a 3Node with IPv4 on Windows](#ssh-into-a-3node-with-ipv4-on-windows)
|
||||
- [SSH into a 3Node with the Planetary Network on Windows](#ssh-into-a-3node-with-the-planetary-network-on-windows)
|
||||
- [Questions and Feedback](#questions-and-feedback)
|
||||
|
||||
***
|
||||
|
||||
# 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).
|
||||
|
||||
To deploy different workloads, the SSH connection process should be very similar.
|
||||
|
||||
If you have any questions, feel free to write a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
|
||||
|
||||
# Main Steps and Prerequisites
|
||||
|
||||
Make sure to [read the introduction](../tfgrid3_getstarted.md#get-started---your-first-deployment) before going further.
|
||||
|
||||
The main steps for the whole process are the following:
|
||||
|
||||
* Create an SSH Key pair
|
||||
* Deploy a 3Node
|
||||
* Choose IPv4 or the Planetary Network
|
||||
* SSH into the 3Node
|
||||
* For the Planetary Network, download the Planetary Network Connector
|
||||
|
||||
|
||||
|
||||
# Step-by-Step Process with OpenSSH
|
||||
|
||||
## Linux
|
||||
|
||||
### SSH into a 3Node with IPv4 on Linux
|
||||
|
||||
Here are the steps to SSH into a 3Node with IPv4 on Linux.
|
||||
|
||||
* To create the SSH key pair, write in the terminal
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in the terminal
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select IPv4 in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the IPv4 address
|
||||
* Open the terminal, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@IPv4_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on Linux with IPv4.
|
||||
|
||||
|
||||
|
||||
### SSH into a 3Node with the Planetary Network on Linux
|
||||
|
||||
Here are the steps to SSH into a 3Node with the Planetary Network on Linux.
|
||||
|
||||
* To download and connect to the Threefold Planetary Network Connector
|
||||
* Download the [.deb file](https://github.com/threefoldtech/planetary_network/releases/tag/v0.3-rc1-Linux)
|
||||
* Right-click and select `Open with other application`
|
||||
* Select `Software Install`
|
||||
* Search the `Threefold Planetary Connector` and open it
|
||||
* Disconnect your VPN if you have one
|
||||
* In the connector, click `Connect`
|
||||
* To create the SSH key pair, write in the terminal
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in the terminal
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select Planetary Network in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the Planetary Network address
|
||||
* Open the terminal, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@planetary_network_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on Linux with the Planetary Network.
|
||||
|
||||
|
||||
|
||||
## MAC
|
||||
|
||||
### SSH into a 3Node with IPv4 on MAC
|
||||
|
||||
Here are the steps to SSH into a 3Node with IPv4 on MAC.
|
||||
|
||||
* To create the SSH key pair, in the terminal write
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in the terminal
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select IPv4 in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the IPv4 address
|
||||
* Open the terminal, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@IPv4_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on MAC with IPv4.
|
||||
|
||||
|
||||
|
||||
### SSH into a 3Node with the Planetary Network on MAC
|
||||
|
||||
Here are the steps to SSH into a 3Node with the Planetary Network on MAC.
|
||||
|
||||
* To download and connect to the Threefold Planetary Network Connector
|
||||
* Download the [.dmg file](https://github.com/threefoldtech/planetary_network/releases/tag/v0.3-rc1-MacOS)
|
||||
* Run the dmg installer
|
||||
* Search the Threefold Planetary Connector in `Applications` and open it
|
||||
* Disconnect your VPN if you have one
|
||||
* In the connector, click `Connect`
|
||||
* To create the SSH key pair, write in the terminal
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in the terminal
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select Planetary Network in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the Planetary Network address
|
||||
* Open the terminal, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@planetary_network_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on MAC with the Planetary Network.
|
||||
|
||||
|
||||
|
||||
## Windows
|
||||
|
||||
### SSH into a 3Node with IPv4 on Windows
|
||||
|
||||
* To download OpenSSH client and OpenSSH server
|
||||
* Open the `Settings` and select `Apps`
|
||||
* Click `Apps & Features`
|
||||
* Click `Optional Features`
|
||||
* Verifiy if OpenSSH Client and OpenSSH Server are there
|
||||
* If not
|
||||
* Click `Add a feature`
|
||||
* Search OpenSSH
|
||||
* Install OpenSSH Client and OpenSSH Server
|
||||
* To create the SSH key pair, open `PowerShell` and write
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in `PowerShell`
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select IPv4 in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the IPv4 address
|
||||
* Open `PowerShell`, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@IPv4_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on Window with IPv4.
|
||||
|
||||
|
||||
|
||||
### SSH into a 3Node with the Planetary Network on Windows
|
||||
|
||||
* To download and connect to the Threefold Planetary Network Connector
|
||||
* Download the [.msi file](https://github.com/threefoldtech/planetary_network/releases/tag/v0.3-rc1-Windows10)
|
||||
* Search the `Threefold Planetary Connector`
|
||||
* Right-click and select `Install`
|
||||
* Disconnect your VPN if you have one
|
||||
* Open the TF connector and click `Connect`
|
||||
* To download OpenSSH client and OpenSSH server
|
||||
* Open the `Settings` and select `Apps`
|
||||
* Click `Apps & Features`
|
||||
* Click `Optional Features`
|
||||
* Verifiy if OpenSSH Client and OpenSSH Server are there
|
||||
* If not
|
||||
* Click `Add a feature`
|
||||
* Search OpenSSH
|
||||
* Install OpenSSH Client and OpenSSH Server
|
||||
* To create the SSH key pair, open `PowerShell` and write
|
||||
* ```
|
||||
ssh-keygen
|
||||
```
|
||||
* Save in default location
|
||||
* Write a password (optional)
|
||||
* To see the public key, write in `PowerShell`
|
||||
* ```
|
||||
cat ~/.ssh/id_rsa.pub
|
||||
```
|
||||
* Select and copy the public key when needed
|
||||
* To deploy a full VM
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select Planetary Network address in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Copy the Planetary Network address
|
||||
* Open `PowerShell`, write the following with the deployment address and write **yes** to confirm
|
||||
* ```
|
||||
ssh root@planetary_network_address
|
||||
```
|
||||
|
||||
You now have an SSH connection on Window with the Planetary Network.
|
||||
|
||||
|
||||
|
||||
# Questions and Feedback
|
||||
|
||||
If you have any questions, let us know by writing a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
@@ -1,81 +0,0 @@
|
||||
<h1> SSH Remote Connection with PuTTY </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Main Steps and Prerequisites](#main-steps-and-prerequisites)
|
||||
- [SSH with PuTTY on Windows](#ssh-with-putty-on-windows)
|
||||
- [Questions and Feedback](#questions-and-feedback)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this Threefold Guide, we show how easy it is to deploy a full virtual machine (VM) and SSH into a 3Node on Windows with [PuTTY](https://www.putty.org/).
|
||||
|
||||
To deploy different workloads, the SSH connection process should be very similar.
|
||||
|
||||
If you have any questions, feel free to write a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
|
||||
|
||||
|
||||
## Main Steps and Prerequisites
|
||||
|
||||
Make sure to [read the introduction](../tfgrid3_getstarted.md#get-started---your-first-deployment) before going further.
|
||||
|
||||
The main steps for the whole process are the following:
|
||||
|
||||
* Create an SSH Key pair
|
||||
* Deploy a 3Node
|
||||
* Choose IPv4 or the Planetary Network
|
||||
* SSH into the 3Node
|
||||
* For the Planetary Network, download the Planetary Network Connector
|
||||
|
||||
|
||||
|
||||
## SSH with PuTTY on Windows
|
||||
|
||||
Here are the main steps to SSH into a full VM using PuTTY on a Windows machine.
|
||||
|
||||
* Download [PuTTY](https://www.putty.org/)
|
||||
* You can download the Windows Installer in .msi format [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html)
|
||||
* This will add both PuTTY and PuTTYgen to your computer
|
||||
* Make sure that you have the latest version of PuTTY to avoid potential issues
|
||||
* Generate an SSH key pair
|
||||
* Open PuTTYgen
|
||||
* In `Parameters`, you can set the type of key to `RSA` or to `EdDSA`
|
||||
* Click on `Generate`
|
||||
* Add a passphrase for your private key (optional)
|
||||
* Take note of the generated SSH public key
|
||||
* You will need to paste it to the Dashboard later
|
||||
* Click `Save private key`
|
||||
* To deploy a full VM
|
||||
* Go to the following section of the [Threefold Dashboard](https://dashboard.grid.tf/): Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select IPv4 in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
* To SSH into the VM once the 3Node is deployed
|
||||
* Take note of the IPv4 address
|
||||
* Connect to the full VM with PuTTY
|
||||
* Open PuTTY
|
||||
* Go to the section `Session`
|
||||
* Add the VM IPv4 address under `Host Name (or IP address)`
|
||||
* Make sure `Connection type` is set to `SSH`
|
||||
* Go to the section `Connection` -> `SSH` -> `Auth` -> `Credentials`
|
||||
* Under `Private key file for authentication`, click on `Browse...`
|
||||
* Look for the generated SSH private key in .ppk format and click `Open`
|
||||
* In the main `PuTTY` window, click `Open`
|
||||
* In the PuTTY terminal window, enter `root` as the login parameter
|
||||
* Enter the passphrase for the private key if you set one
|
||||
|
||||
You now have an SSH connection on Windows using PuTTY.
|
||||
|
||||
|
||||
|
||||
## Questions and Feedback
|
||||
|
||||
If you have any questions, let us know by writing a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
@@ -1,129 +0,0 @@
|
||||
<h1> WireGuard Access </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Deploy a Weblet with WireGuard Access](#deploy-a-weblet-with-wireguard-access)
|
||||
- [Install WireGuard](#install-wireguard)
|
||||
- [Set the WireGuard Configurations](#set-the-wireguard-configurations)
|
||||
- [Linux and MAC](#linux-and-mac)
|
||||
- [Windows](#windows)
|
||||
- [Test the WireGuard Connection](#test-the-wireguard-connection)
|
||||
- [SSH into the Deployment with Wireguard](#ssh-into-the-deployment-with-wireguard)
|
||||
- [Questions and Feedback](#questions-and-feedback)
|
||||
|
||||
***
|
||||
|
||||
# Introduction
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
# Prerequisites
|
||||
|
||||
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)
|
||||
* [PuTTy](ssh_putty.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.
|
||||
|
||||
* On the [Threefold Dashboard](https://dashboard.grid.tf/), go to: Deploy -> Virtual Machines -> Full Virtual Machine
|
||||
* Choose the parameters you want
|
||||
* Minimum CPU: 1 vCore
|
||||
* Minimum Memory: 512 Mb
|
||||
* Minimum Disk Size: 15 Gb
|
||||
* Select `Add WireGuard Access` in `Network`
|
||||
* In `Node Selection`, click on `Load Nodes`
|
||||
* Click `Deploy`
|
||||
|
||||
Once the Full VM is deployed, a window named **Details** will appear. You will need to take note of the **WireGuard Config** to set the WireGuard configurations and the **WireGuard IP** to SSH into the deployment.
|
||||
|
||||
> Note: At anytime, you can open the **Details** window by clicking on the button **Show Details** under **Actions** on the Dashboard weblet page.
|
||||
|
||||
|
||||
|
||||
# Install WireGuard
|
||||
|
||||
To install WireGuard, please refer to the official [WireGuard installation documentation](https://www.wireguard.com/install/).
|
||||
|
||||
|
||||
|
||||
# Set the WireGuard Configurations
|
||||
|
||||
When it comes to setting the WireGuard configurations, the steps are similar for Linux and MAC, but differ slightly for Windows. For Linux and MAC, we will be using the CLI. For Windows, we will be using the WireGuard GUI app.
|
||||
|
||||
## Linux and MAC
|
||||
|
||||
To set the WireGuard connection on Linux or MAC, create a WireGuard configuration file and run WireGuard via the command line:
|
||||
|
||||
* Copy the content **WireGuard Config** from the Dashboard **Details** window
|
||||
* Paste the content to a file with the extension `.conf` (e.g. **wg.conf**) in the directory `/etc/wireguard`
|
||||
* ```
|
||||
sudo nano /etc/wireguard/wg.conf
|
||||
```
|
||||
* Start WireGuard with the command **wg-quick** and, as a parameter, pass the configuration file without the extension (e.g. *wg.conf -> wg*)
|
||||
* ```
|
||||
wg-quick up wg
|
||||
```
|
||||
* Note that you can also specify a config file by path, stored in any location
|
||||
* ```
|
||||
wg-quick up /etc/wireguard/wg.conf
|
||||
```
|
||||
* If you want to stop the WireGuard service, you can write the following in the terminal
|
||||
* ```
|
||||
wg-quick down wg
|
||||
```
|
||||
|
||||
> Note: If it doesn't work and you already did a WireGuard connection with the same file, write on the terminal `wg-quick down wg`, then `wg-quick up wg` to reset the connection with new configurations.
|
||||
|
||||
## Windows
|
||||
|
||||
To set the WireGuard connection on Windows, add and activate a tunnel with the WireGuard app:
|
||||
|
||||
* Open the WireGuard GUI app
|
||||
* Click on **Add Tunnel** and then **Add empty tunnel**
|
||||
* Choose a name for the tunnel
|
||||
* Erase the content of the main window and paste the content **WireGuard Config** from the Dashboard **Details** window
|
||||
* Click **Save** and then click on **Activate**.
|
||||
|
||||
|
||||
|
||||
|
||||
# Test the WireGuard Connection
|
||||
|
||||
As a test, you can [ping](../../computer_it_basics/cli_scripts_basics.md#test-the-network-connectivity-of-a-domain-or-an-ip-address-with-ping) the virtual IP address of the VM to make sure the WireGuard connection is properly established. Make sure to replace `VM_WireGuard_IP` with the proper WireGuard IP address:
|
||||
|
||||
* Ping the deployment
|
||||
* ```
|
||||
ping VM_WireGuard_IP
|
||||
```
|
||||
|
||||
|
||||
|
||||
# SSH into the Deployment with Wireguard
|
||||
|
||||
To SSH into the deployment with Wireguard, use the **WireGuard IP** shown in the Dashboard **Details** window.
|
||||
|
||||
* SSH into the deployment
|
||||
* ```
|
||||
ssh root@VM_WireGuard_IP
|
||||
```
|
||||
|
||||
You now have access to the deployment over a WireGuard SSH connection.
|
||||
|
||||
|
||||
|
||||
# Questions and Feedback
|
||||
|
||||
If you have any questions, let us know by writing a post on the [Threefold Forum](http://forum.threefold.io/) or by reaching out to the [ThreeFold Grid Tester Community](https://t.me/threefoldtesting) on Telegram.
|
||||
@@ -1,89 +0,0 @@
|
||||
<h1> SSH Remote Connection with WSL </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [SSH Key Generation](#ssh-key-generation)
|
||||
- [Connect to Remote Host with SSH](#connect-to-remote-host-with-ssh)
|
||||
- [Enable Port 22 in Windows Firewall](#enable-port-22-in-windows-firewall)
|
||||
- [Questions and Feedback](#questions-and-feedback)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this Threefold Guide, we show how easy it is to SSH into a 3node on Windows with [Windows Subsystem for Linux (WSL)](https://ubuntu.com/wsl).
|
||||
|
||||
If you have any questions, feel free to write a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
|
||||
## SSH Key Generation
|
||||
|
||||
Make sure SSH is installed by entering following command at the command prompt:
|
||||
|
||||
```sh
|
||||
sudo apt install openssh-client
|
||||
```
|
||||
|
||||
The key generation process is identical to the process on a native Linux or Ubuntu installation.
|
||||
With SSH installed, run the SSH key generator by typing the following:
|
||||
|
||||
```sh
|
||||
ssh-keygen -t rsa
|
||||
```
|
||||
|
||||
Then choose the key name and passphrase or simply press return twice to accept the default values (`key name = id_rsa` and `no passphrase`).
|
||||
When the process has finished, the private key and the public key can be found in the `~/.ssh` directory accessible from the Ubuntu terminal.
|
||||
You can also access the key from Windows file manager in the following folder:
|
||||
|
||||
```sh
|
||||
\\wsl$\\Ubuntu\home\<username>\.ssh\
|
||||
```
|
||||
|
||||
Your private key will be generated using the default name (`id_rsa`) or the filename you specified.
|
||||
The corresponding public key will be generated using the same filename but with a `.pub` extension added.
|
||||
If you open the public key in a text editor it should contain something similar to this:
|
||||
|
||||
```
|
||||
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDNqqi1mHLnryb1FdbePrSZQdmXRZxGZbo0gTfglysq6KMNUNY2VhzmYN9JYW39yNtjhVxqfW6ewc+eHiL+IRRM1P5ecDAaL3V0ou6ecSurU+t9DR4114mzNJ5SqNxMgiJzbXdhR+j55GjfXdk0FyzxM3a5qpVcGZEXiAzGzhHytUV51+YGnuLGaZ37nebh3UlYC+KJev4MYIVww0tWmY+9GniRSQlgLLUQZ+FcBUjaqhwqVqsHe4F/woW1IHe7mfm63GXyBavVc+llrEzRbMO111MogZUcoWDI9w7UIm8ZOTnhJsk7jhJzG2GpSXZHmly/a/buFaaFnmfZ4MYPkgJD username@example.com
|
||||
```
|
||||
|
||||
Copying the entire text you can specify your public SSH key while connecting your wallet before deploying a VM.
|
||||
|
||||
## Connect to Remote Host with SSH
|
||||
|
||||
With the SSH key you should be able to SSH to your account on the remote system from the computer that has your private key using the following command:
|
||||
|
||||
```sh
|
||||
ssh username@remote_IP_host
|
||||
```
|
||||
|
||||
If the private key you're using does not have the default name, or is not stored in the default path (not `~/.ssh/id_rsa`), you must explicitly invoke it!
|
||||
On the SSH command line add the `-i` flag and the path to your private key.
|
||||
For example, to invoke the private key `my_key`, stored in the `~/.ssh/keys` directory, when connecting to your account on a remote host, enter:
|
||||
|
||||
```sh
|
||||
ssh -i ~/.ssh/keys/my_key username@remote_IP_host
|
||||
```
|
||||
|
||||
## Enable Port 22 in Windows Firewall
|
||||
|
||||
The port 22 is used for Secure Shell (SSH) communication and allows remote administration access to the VM.
|
||||
Sometimes it needs and can be unblocked as follows:
|
||||
|
||||
- open Windows Firewall Advance Settings
|
||||
- click on `New Rule…` under `Inbound Rules` to create a new firewall rule
|
||||
- under `Rule Type` select `Port`
|
||||
- under `Protocol and Ports` select `TCP`, `Specific local Ports` and enter `22`
|
||||
- under `Action` select `Allow the connection`
|
||||
- under `Profile` make sure to only select `Domain` and `Private`
|
||||
|
||||
NB: do not select `Public` unless you absolutely require a direct connection form the outside world.
|
||||
This is not recommend especially for portable device (Laptop, Tablets) that connect to random Wi-fi hotspots.
|
||||
|
||||
- under `Name`
|
||||
- Name: `SSH Server`
|
||||
- Description: `SSH Server`
|
||||
|
||||
## Questions and Feedback
|
||||
|
||||
If you have any questions, let us know by writing a post on the [Threefold Forum](http://forum.threefold.io/).
|
||||
@@ -1,32 +0,0 @@
|
||||
# TFGrid Manual - Get Started
|
||||
|
||||
## Get Started - Your First Deployment
|
||||
|
||||
It's easy to get started on the TFGrid and deploy applications.
|
||||
|
||||
- [Create a TFChain Account](../../dashboard/wallet_connector.md)
|
||||
- [Get TFT](../../threefold_token/buy_sell_tft/buy_sell_tft.md)
|
||||
- [Bridge TFT to TChain](../../threefold_token/tft_bridges/tft_bridges.md)
|
||||
- [Deploy an Application](../../dashboard/deploy/deploy.md)
|
||||
- [SSH Remote Connection](./ssh_guide/ssh_guide.md)
|
||||
- [SSH with OpenSSH](./ssh_guide/ssh_openssh.md)
|
||||
- [SSH with PuTTY](./ssh_guide/ssh_putty.md)
|
||||
- [SSH with WSL](./ssh_guide/ssh_wsl.md)
|
||||
- [SSH and WireGuard](./ssh_guide/ssh_wireguard.md)
|
||||
|
||||
## Grid Platforms
|
||||
|
||||
- [TF Dashboard](../../dashboard/dashboard.md)
|
||||
- [TF Flist Hub](../../developers/flist/flist_hub/zos_hub.md)
|
||||
|
||||
## TFGrid Services and Resources
|
||||
|
||||
- [TFGrid Services](./tfgrid_services/tf_grid_services_readme.md)
|
||||
|
||||
## Advanced Deployment Techniques
|
||||
|
||||
- [Advanced Topics](../advanced/advanced.md)
|
||||
|
||||
***
|
||||
|
||||
If you have any question, feel free to ask for help on the [Threefold Forum](https://forum.threefold.io/c/threefold-grid-utilization/support/).
|
||||
@@ -1,23 +0,0 @@
|
||||
|
||||
|
||||
# TFGrid Network Concepts
|
||||
|
||||
## Peer 2 Peer Private Network
|
||||
|
||||
|
||||
|
||||
All Zmachines (or kubernetes nodes) are connected to each other over private networks.
|
||||
|
||||
When you use IAC or our clients then you can manually specify the name and IP Network Addr to be used.
|
||||
|
||||
## The Planetary Network
|
||||
|
||||
## Web Gateway (experts only)
|
||||
|
||||
|
||||
|
||||
## More Info
|
||||
|
||||
- [Planetary Network](https://library.threefold.me/info/threefold#/technology/threefold__planetary_network)
|
||||
- [Web Gateway](https://library.threefold.me/info/threefold#/technology/threefold__webgw)
|
||||
- [Z-Net = secure network between Z-Machines](https://library.threefold.me/info/threefold#/technology/threefold__znet)
|
||||
@@ -1,8 +0,0 @@
|
||||
# TFGrid Storaeg Concepts
|
||||
|
||||
|
||||
|
||||
|
||||
## ThreeFold Flist HUB
|
||||
|
||||
see https://hub.grid.tf/
|
||||
@@ -1,58 +0,0 @@
|
||||
# TFGrid 3.0 Whats There To Know
|
||||
|
||||
- [Storage Concepts](./tfgrid3_storage_concepts.md)
|
||||
- [Network Concepts](./tfgrid3_network_concepts.md)
|
||||
|
||||
## Networking
|
||||
|
||||
### Private network (ZNET)
|
||||
|
||||
For a project that needs a private network, we need a network that can span across multiple nodes, this can be achieved by the network workload reservation [Network](/getstarted/tfgrid3_network_concepts.md)
|
||||
|
||||
### Planetary network
|
||||
|
||||
For a project that want their workloads directly connected to the planetary network we will need the option planetary enabled when deploying a VM or kubernetes. Check [Planetary network](https://library.threefold.me/info/threefold#/technology/threefold__planetary_network) for more info about
|
||||
|
||||
### Public IPs
|
||||
When you want to have a public IP assigned to your workload, you need to reserve the number of IPs along with your contract and then you can attach it to the VM workload
|
||||
|
||||
## Exposing the workloads to the public
|
||||
|
||||
Typically, if you reserved a public IP you can do that directly and create a domain referencing you public IP. Threefold provides also [Webgateway technology](https://library.threefold.me/info/threefold#/technology/threefold__webgw) a very cost-efficient technology to help with exposing your workloads
|
||||
|
||||
### how it works
|
||||
Basically you create a `domain reservation` that can be
|
||||
- `prefix` based e.g `mywebsite` that will internally translate to `mywebsite.ghent01.devnet.grid.tf`
|
||||
- `full domain` e.g `mysuperwebsite.com` (this needs to point to the gateway IP)
|
||||
|
||||
And then you need to specify the yggrassil IP of your backend service, so the gateway knows where to redirect the traffic
|
||||
|
||||
#### TLS
|
||||
As a user, you have two options
|
||||
- let the gateway terminate the TLS traffic for you and communicate with your workloads directly
|
||||
- let the gateway forward the traffic to your backend and you do the termination yourself (the recommended way if you are doing any sensitive business)
|
||||
|
||||
|
||||
## Compute
|
||||
|
||||
VM workload is the only workload that you will need to run a full blown VM or an [flist-based](/flist_hub/flist_hub.md) container
|
||||
|
||||
### How can I create an flist?
|
||||
|
||||
The easiest way is by converting existing docker images using [the hub](https://hub.grid.tf/docker-convert)
|
||||
|
||||
|
||||
### How flist-based container run in a VM?
|
||||
ZOS injects its own generic kernel while booting the container based on the content of the filesystem
|
||||
|
||||
### kubernetes
|
||||
We leverage the VM primitive to allow provisioning kubernetes clusters across multiple nodes based on k3os flist.
|
||||
|
||||
|
||||
## Exploring the capacity
|
||||
You can easily check using [explorer-ui](dashboard/explorer/explorer_home.md) , also to plan your deployment you can use these [example queries](dashboard/explorer/explorer_graphql_examples.md)
|
||||
|
||||
## Getting started
|
||||
|
||||
Please check [Getting started](/getstarted/tfgrid3_getstarted.md) to get the necessary software / configurations
|
||||
|
||||
@@ -1,95 +0,0 @@
|
||||
<h1> ThreeFold Grid Services </h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Devnet](#devnet)
|
||||
- [QAnet](#qanet)
|
||||
- [Testnet](#testnet)
|
||||
- [Mainnet](#mainnet)
|
||||
- [Supported Planetary Network Nodes](#supported-planetary-network-nodes)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
On this article we have aggregated a list of all of the services running on Threefold Grid 3 infrastructure for your convenience
|
||||
|
||||
> Note: the usage of `dev` indicates a devnet service.
|
||||
> and usage of `test` indicates a testnet service.
|
||||
|
||||
## Devnet
|
||||
|
||||
- [TFChain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2F/tfchain.dev.grid.tf#/explorer) `wss://tfchain.dev.grid.tf`
|
||||
- [GraphQL](https://graphql.dev.grid.tf/graphql)
|
||||
- [Activation Service](https://activation.dev.grid.tf/activation/)
|
||||
- [TFGrid Proxy](https://gridproxy.dev.grid.tf)
|
||||
- [Grid Dashboard](https://dashboard.dev.grid.tf)
|
||||
|
||||
|
||||
## QAnet
|
||||
|
||||
- [TFChain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2F/tfchain.qa.grid.tf#/explorer) `wss://tfchain.qa.grid.tf`
|
||||
- [GraphQL](https://graphql.qa.grid.tf/graphql)
|
||||
- [Activation Service](https://activation.qa.grid.tf/activation/)
|
||||
- [TFGrid Proxy](https://gridproxy.qa.grid.tf)
|
||||
- [Grid Dashboard](https://dashboard.qa.grid.tf)
|
||||
|
||||
## Testnet
|
||||
|
||||
- [TFChain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2F/tfchain.test.grid.tf#/explorer) `wss://tfchain.test.grid.tf`
|
||||
- [GraphQL](https://graphql.test.grid.tf/graphql)
|
||||
- [Activation Service](https://activation.test.grid.tf/activation/)
|
||||
- [TFGrid Proxy](https://gridproxy.test.grid.tf)
|
||||
- [Grid Dashboard](https://dashboard.test.grid.tf)
|
||||
|
||||
## Mainnet
|
||||
|
||||
- [TFChain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2F/tfchain.grid.tf#/explorer) `wss://tfchain.grid.tf`
|
||||
- [GraphQL](https://graphql.grid.tf/graphql)
|
||||
- [Activation Service](https://activation.grid.tf/activation/)
|
||||
- [TFChain-Stellar Bridge](https://bridge.bsc.threefold.io/)
|
||||
- [TFChain-Ethereum Bridge](https://bridge.eth.threefold.io/)
|
||||
- [TFGrid Proxy](https://gridproxy.grid.tf)
|
||||
- [Grid Dashboard](https://dashboard.grid.tf)
|
||||
|
||||
### Supported Planetary Network Nodes
|
||||
|
||||
```
|
||||
Peers:
|
||||
[
|
||||
# Threefold Lochrist
|
||||
tcp://gent01.grid.tf:9943
|
||||
tcp://gent02.grid.tf:9943
|
||||
tcp://gent03.grid.tf:9943
|
||||
tcp://gent04.grid.tf:9943
|
||||
tcp://gent01.test.grid.tf:9943
|
||||
tcp://gent02.test.grid.tf:9943
|
||||
tcp://gent01.dev.grid.tf:9943
|
||||
tcp://gent02.dev.grid.tf:9943
|
||||
# GreenEdge
|
||||
tcp://gw291.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw293.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw294.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw297.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw298.vienna1.greenedgecloud.com:9943
|
||||
tcp://gw299.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw300.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw304.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw306.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw307.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw309.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw313.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw324.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw326.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw327.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw328.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw330.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw331.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw333.salzburg1.greenedgecloud.com:9943
|
||||
tcp://gw422.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw423.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw424.vienna2.greenedgecloud.com:9943
|
||||
tcp://gw425.vienna2.greenedgecloud.com:9943
|
||||
]
|
||||
```
|
||||
Reference in New Issue
Block a user