add docs

docs/client/basic-authentication.md

@@ -1,6 +1,6 @@
 ---
 title: Basic Authentication
-order: 2
+order: 4
 ---
 
 # Sharing sites with basic authentication

docs/client/configuration.md

@@ -1,6 +1,6 @@
 ---
 title: Configuration
-order: 3
+order: 6
 ---
 
 # Configuration

docs/client/dashboard.md

@@ -1,6 +1,6 @@
 ---
-title: Dashboard
-order: 5
+title: Local Dashboard
+order: 2
 ---
 
 # Dashboard

docs/client/global-server-infrastructure.md

@@ -0,0 +1,44 @@
+---
+title: Global Server Infrastructure
+order: 4
+---
+
+# Global Server Infrastructure ::pro
+
+[Expose Pro](/get-pro) allows you to choose between multiple Expose servers around the world, so that you can use an endpoint closest to you.
+
+To get a list of all the available Expose servers, you can run `expose servers`
+
+```
+$ expose servers
+
++------+---------------------------+------+
+| Key  | Region                    | Type |
++------+---------------------------+------+
+| eu-1 | EU (Frankfurt)            | Pro  |
+| us-1 | US (New York)             | Pro  |
+| us-2 | US (San Francisco)        | Pro  |
+| ap-1 | Asia Pacific (Singapore)  | Pro  |
+| in-1 | India (Bangalore)         | Pro  |
+| sa-1 | South America (São Paulo) | Pro  |
+| au-1 | Australia (Sydney)        | Pro  |
++------+---------------------------+------+
+```
+
+## Changing servers
+
+When you share a local URL, or a local TCP port, you can specify the Expose server region, using the `--server` command line option. Pass the server key as the option to connect to this specific server.
+
+```bash
+expose share my-local-site.test --server=eu-1
+```
+
+## Setting a default server
+
+Most of the time you will want to always use the server location that is closest to you for all of your Expose commands. You can define the default server that Expose should use, by calling the `expose default-server` command:
+
+```bash
+expose default-server us-2
+```
+
+Now the next time that you will share a local URL or port, Expose is automatically going to connect to the `us-2` server for your.

docs/client/sharing-tcp-ports.md

@@ -0,0 +1,18 @@
+---
+title: Sharing TCP ports
+order: 3
+---
+
+# Sharing TCP Ports ::pro
+
+Expose not only allows you to share your local development URLs, but you can also use Expose to share any of your local TCP ports.
+
+For example, you might want to share your local copy of [HELO](https://usehelo.com) so that your PHP application can send test emails right through your local SMTP server.
+
+You can share a local TCP port by calling `share-port` followed by the local port number that you want to share:
+
+```bash
+expose share-port 2525
+```
+
+The Expose server will assign a random TCP port that you can then use on other servers and services to connect to the tunnel.

docs/client/sharing.md

@@ -38,17 +38,17 @@ If your local sites are not available at `foldername.test` you can explicitly sh
 This is required when sharing sites that have HTTPS locally or Expose can't map local directory names to URLs automatically.
 
 ```bash
-# Will share access to http://192.168.2.100 using a randomly generated subdomain
+# Will share access to http://192.168.2.100
 expose share http://192.168.2.100
 
-# Will share access to http://my-local-site.dev using a randomly generated subdomain
+# Will share access to http://my-local-site.dev
 expose share my-local-site.dev
 
-# Will share access to https://my-local-site.dev using a randomly generated subdomain (note the https)
+# Will share access to https://my-local-site.dev
 expose share https://my-local-site.dev
 ```
 
-## Share a local site with a given subdomain
+## Share a local site with a given subdomain ::pro
 
 You can also share one of your local sites explicitly and specify the exact subdomain that you want to use when sharing the site. This is very useful if you are testing webhooks and want to use the same webhook configuration and don't update the webhook endpoints on every Expose connect. Custom subdomains require an own Expose server in your infrastructure or Expose Pro.