Move the documentation repository to a public repo

Added a LICENSE and documentation on how to contribute

Updated CI/CD to use the root level code

docs/examples/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Examples",
+  "position": 4
+}

docs/examples/aws-ecs-client-daemon.md

@@ -0,0 +1,92 @@
+---
+sidebar_position: 1
+---
+
+# NetBird Client on AWS ECS (Terraform)
+
+<p align="center">
+    <img src="/docs/img/examples/wiretrustee-on-aws-ecs.png" alt="high-level-dia" width="400"/>
+</p>
+
+A common way to run containers in the AWS cloud is to use Elastic Container Service (ECS).
+ECS is a fully managed container orchestration service that makes it easy to deploy, manage, and scale containerized applications. 
+
+It is best practice and common to run this infrastructure behind security guardrails like strict security groups and private subnets.
+
+Also, a routine for many System's administrators and Developers, is to connect to servers that run their company's software in order to troubleshoot, validate output and even install dependencies.
+If you have your systems running in a private network, you got a few options to allow communication to hosts in that network:
+* Add a [bastion host](https://en.wikipedia.org/wiki/Bastion_host) or [jump server](https://en.wikipedia.org/wiki/Jump_server).
+* Connect a [site-2-site](https://en.wikipedia.org/wiki/Virtual_private_network#Types) VPN.
+* [Remote access](https://en.wikipedia.org/wiki/Virtual_private_network#Types) VPN.
+* Allow IP(s) address in the server's security group.
+
+All these options are valid and proved to work over the years, but they come with some costs that in the short to mid-term you start to deal with:
+* Hard implementation.
+* Fragile firewall configuration.
+* Yet, another server to secure and maintain.
+
+**In this example, we will run NetBird client configured as a daemon set in ECS deployed with Terraform.**
+
+This allows you to:
+
+* Run NetBird as an ECS native service, you can manage and maintain it the same way you do with your other services.
+* Connect to EC2 running on private subnets without the need to open firewall rules or configure bastion servers.
+* Access other services connected to your NetBird network and running anywhere.
+
+## Requirements
+* Terraform > 1.0.
+* A NetBird account with a Setup Key.
+* Another NetBird client in your network to validate the connection (possibly your laptop or a machine you are running this example on).
+* The [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) installed.
+* An [AWS account](https://aws.amazon.com/free/).
+* Your AWS credentials. You can [create a new Access Key on this page](https://console.aws.amazon.com/iam/home?#/security_credentials).
+## Notice
+> Before getting started with this example, be aware that creating the resources from it may incur charges from AWS.
+
+## Getting started
+
+Clone this repository, download, and install Terraform following the guide [here](https://learn.hashicorp.com/tutorials/terraform/install-cli?in=terraform/aws-get-started).
+
+Login to https://app.netbird.io and [add your machine as a peer](https://app.netbird.io/add-peer), once you are done with the steps described there, copy your [Setup key](https://app.netbird.io/setup-keys).
+
+Using a text editor, edit the [variables.tf](https://github.com/wiretrustee/wiretrustee-examples/tree/master/ecs-client-daemon/variables.tf) file, and update the `wt_setup_key` variable with your setup key. Also, make sure that `ssh_public_key_path` variable is pointing to the correct public key path. If necessary, update the remaining variables according to your requirements and their descriptions.
+
+Before continuing, you may also update the [provider.tf](https://github.com/wiretrustee/wiretrustee-examples/tree/master/ecs-client-daemon/provider.tf) to configure proper AWS region and default tags.
+
+### Creating the resources with Terraform
+Follow the steps below to run terraform and create your test environment:
+
+1. From the root of the cloned repository, enter the ecs-client-daemon folder and run terraform init to download the modules and providers used in this example.
+```shell
+cd ecs-client-daemon
+terraform init
+```
+2. Run terraform plan to get the estimated changes
+```shell
+terraform plan -out plan.tf
+```
+3. Run terraform apply to create your infrastructure
+```shell
+terraform apply plan.tf
+``` 
+
+### Validating the deployment
+After a few minutes, the autoscaling group will launch an EC2 instance and there you will find the NetBird's ECS Daemon service running. With that, we can go to our [NetBird dashboard](https://app.netbird.io) and pick the IP of the node that is running NetBird, then we can connect to the node via ssh. For Unix(s) systems:
+```shell
+ssh ec2-user@100.64.0.200
+``` 
+Once you've login, you should be able to see the containers running by using the docker command:
+```shell
+sudo docker ps
+```
+
+### Deleting the infrastructure resources used in the example
+Once you are done validating the example, you can remove the resources with the following steps:
+1. Run terraform plan with the flag `-destroy`
+```shell
+terraform plan -out plan.tf -destroy
+```
+2. Then execute the apply command:
+```shell
+terraform apply plan.tf
+```

docs/examples/netbird-docker.md

@@ -0,0 +1,27 @@
+---
+sidebar_position: 2
+---
+
+# NetBird Client in Docker
+
+One of the simplest ways of running NetBird client application is to use a pre-built [Docker image](https://hub.docker.com/r/netbirdio/netbird).
+
+**Prerequisites:**
+* **Docker installed.** 
+   If you don't have docker installed, please refer to the installation guide on the official [Docker website](https://docs.docker.com/get-docker/).
+* **NetBird account.** 
+   Register one at [app.netbird.io](https://app.netbird.io/).
+
+You would need to obtain a [setup key](/overview/setup-keys) to associate NetBird client with your account.
+
+The setup key could be found in the NetBird Management dashboard under the Setup Keys tab - [https://app.netbird.io/setup-keys](https://app.netbird.io/setup-keys).
+
+Set the ```WT_SETUP_KEY``` environment variable and run the command. 
+
+```bash
+docker run --rm --privileged -d -e WT_SETUP_KEY=<SETUP KEY> -v netbird-client:/etc/netbird netbirdio/netbird:latest
+```
+
+That is it! Enjoy using NetBird.
+
+If you would like to learn how to run NetBird Client as an ECS agent on AWS, please refer to [this guide](/examples/aws-ecs-client-daemon).