dashboard / docs / docs: global docs #42 rss

 1diff --git a/main.go b/main.go
 2index 2065890..17c48dc 100644
 3--- a/main.go
 4+++ b/main.go
 5@@ -149,6 +149,11 @@ func main() {
 6 						Href: "/faq",
 7 						Page: pager("faq.md"),
 8 					},
 9+					{
10+						Text: "Regions",
11+						Href: "/regions",
12+						Page: pager("regions.md"),
13+					},
14 					{
15 						Text: "IRC",
16 						Href: "/irc",

 1diff --git a/posts/pgs.md b/posts/pgs.md
 2index e20446c..44670fe 100644
 3--- a/posts/pgs.md
 4+++ b/posts/pgs.md
 5@@ -492,17 +492,23 @@ Then open your browser to http://localhost:1337
 6 
 7 # Caching
 8 
 9-To improve the page speed, pgs sites are cached for 10 minutes by default. This is controlled by the [`Cache-Control: max-age=600` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control) which you can [override with a `_headers` file](#headers).
10+To improve the page speed, pgs sites are cached for 10 minutes by default. This
11+is controlled by the
12+[`Cache-Control: max-age=600` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control)
13+which you can [override with a `_headers` file](#headers).
14 
15-There are two levels of caching: server-side and client-side. The server-side cache is automatically cleared every time you upload files, but client-side caches only expire when `max-age` seconds pass, or if you force-reload or clear your browser cache manually.
16+There are two levels of caching: server-side and client-side. The server-side
17+cache is automatically cleared every time you upload files, but client-side
18+caches only expire when `max-age` seconds pass, or if you force-reload or clear
19+your browser cache manually.
20 
21-In case of issues, you can manually clear the server-side cache with `ssh pgs.sh cache project-name`.
22+In case of issues, you can manually clear the server-side cache with
23+`ssh pgs.sh cache project-name`.
24 
25 # Does pages have a CDN or multi-region support?
26 
27-At this point in time, we are able to serve content from a single VM. If this
28-service gains traction we will commit to having a CDN with multiple regions in
29-the US and EU.
30+Yes, we run pages in multiple regions, internationally. See our
31+[regions page](/regions) to learn more.
32 
33 # Removing a project
34 

 1diff --git a/posts/regions.md b/posts/regions.md
 2new file mode 100644
 3index 0000000..30afc40
 4--- /dev/null
 5+++ b/posts/regions.md
 6@@ -0,0 +1,22 @@
 7+---
 8+title: Regions
 9+description: Where are our services located?
10+keywords: [pico, services, pgs, tuns]
11+toc: 1
12+---
13+
14+- Ashburn, Virginia ([oci](https://cloud.oracle.com))
15+- Amsterdam, Netherlands ([netcup](https://www.netcup.com))
16+
17+# Service Locations
18+
19+- pgs.sh (us, eu)
20+- tuns.sh (us)
21+- eu.tuns.sh (eu)
22+- pipe.pico.sh (us)
23+- prose.sh (us)
24+- pastes.sh (us)
25+- rss-to-emal (us)
26+
27+As demand for our services increases we will increase our service location
28+coverage.

 1diff --git a/posts/tuns.md b/posts/tuns.md
 2index 7afc569..b73e198 100644
 3--- a/posts/tuns.md
 4+++ b/posts/tuns.md
 5@@ -57,6 +57,19 @@ ssh -R dev:80:localhost:8000 tuns.sh
 6 # now anyone can access it at https://{user}-dev.tuns.sh
 7 ```
 8 
 9+# Regions
10+
11+We do **not** have geographical-based routing for tuns.sh.
12+
13+However, we do provide a way for users to pick a server location. With that we
14+have a couple options:
15+
16+- tuns.sh (us, virginia)
17+- eu.tuns.sh (eu, amsterdam)
18+
19+As usage and demand increases we will add more regions. See [regions](/regions)
20+for our official list.
21+
22 # User namespace
23 
24 When creating a tunnel to `tuns` we always prefix the name with your username: