dashboard / erock/docs / docs: global docs #42 rss

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

diff --git a/main.go b/main.go
index 2065890..17c48dc 100644
--- a/main.go
+++ b/main.go
@@ -149,6 +149,11 @@ func main() {
 						Href: "/faq",
 						Page: pager("faq.md"),
 					},
+					{
+						Text: "Regions",
+						Href: "/regions",
+						Page: pager("regions.md"),
+					},
 					{
 						Text: "IRC",
 						Href: "/irc",

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

diff --git a/posts/pgs.md b/posts/pgs.md
index e20446c..44670fe 100644
--- a/posts/pgs.md
+++ b/posts/pgs.md
@@ -492,17 +492,23 @@ Then open your browser to http://localhost:1337
 
 # Caching
 
-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).
+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).
 
-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.
+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.
 
-In case of issues, you can manually clear the server-side cache with `ssh pgs.sh cache project-name`.
+In case of issues, you can manually clear the server-side cache with
+`ssh pgs.sh cache project-name`.
 
 # Does pages have a CDN or multi-region support?
 
-At this point in time, we are able to serve content from a single VM. If this
-service gains traction we will commit to having a CDN with multiple regions in
-the US and EU.
+Yes, we run pages in multiple regions, internationally. See our
+[regions page](/regions) to learn more.
 
 # Removing a project
 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

diff --git a/posts/regions.md b/posts/regions.md
new file mode 100644
index 0000000..5960278
--- /dev/null
+++ b/posts/regions.md
@@ -0,0 +1,22 @@
+---
+title: Regions
+description: Where are our services located?
+keywords: [pico, services, pgs, tuns]
+toc: 1
+---
+
+- Ashburn, Virginia ([oci](https://cloud.oracle.com))
+- Amsterdam, Netherlands ([netcup](https://www.netcup.com))
+
+# Service Locations
+
+- pgs.sh (us, eu)
+- tuns.sh (us)
+- eu.tuns.sh (eu)
+- pipe.pico.sh (us)
+- prose.sh (us)
+- pastes.sh (us)
+- feeds.pico.sh (us)
+
+As demand for our services increases we will increase our service location
+coverage.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

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