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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

diff --git a/posts/pgs.md b/posts/pgs.md
index 329eed5..850ef8b 100644
--- a/posts/pgs.md
+++ b/posts/pgs.md
@@ -26,6 +26,7 @@ The easiest way to deploy static sites on the web.
 - [Image manipulation API](/images#image-manipulation)
 - [Private projects](#access-control-list)
 - [No bandwidth limitations](/faq#are-there-any-bandwidth-limitations)
+- Multi-region support
 
 ## Demo
 
@@ -53,6 +54,13 @@ Use our CLI to manage projects:
 ssh pgs.sh help
 ```
 
+# Regions
+
+> pgs.sh is a global service!
+
+See our [regions page](/regions) to learn more about our geographical service
+coverage.
+
 # Instant promotion and rollback
 
 Additionally you can setup a pipeline for promotion and rollbacks, which will
@@ -505,12 +513,6 @@ your browser cache manually.
 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.
-
 # Removing a project
 
 The _only_ way to delete a project and its contents is with our remote cli:
@@ -541,8 +543,8 @@ running the [rm command](#removing-a-project)
 The `prose` site is automatically generated when users upload images to their
 [prose](/prose) blog.
 
-It is protected, meaning users are **not** allowed to delete it. For all intents and
-purposes users should just ignore it.
+It is protected, meaning users are **not** allowed to delete it. For all intents
+and purposes users should just ignore it.
 
 However, just know, if you make changes to this project it will effect your
 blog. So if you upload images to it then you'll be able to reference those

 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

diff --git a/posts/regions.md b/posts/regions.md
new file mode 100644
index 0000000..b1f9918
--- /dev/null
+++ b/posts/regions.md
@@ -0,0 +1,25 @@
+---
+title: Regions
+description: Where are our services located?
+keywords: [pico, services, pgs, tuns, global, international]
+toc: 1
+---
+
+As of **2025/01** we have two locations:
+
+- Ashburn, Virginia ([oci](https://cloud.oracle.com))
+- Nuremberg, Germany ([netcup](https://www.netcup.com))
+
+Service Locations:
+
+- pgs.sh (us, eu)
+- tuns.sh (us)
+- nue.tuns.sh (eu)
+- pipe.pico.sh (us)
+- prose.sh (us)
+- feeds.pico.sh (us)
+- pastes.sh (us)
+
+We are closely monitoring demand for more regions at pico. Our goal is to
+provide excellent service latency for all users. Feel free to
+[contact us](/contact) with recommendations on new locations.

 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

diff --git a/posts/tuns.md b/posts/tuns.md
index b639717..b32d49e 100644
--- a/posts/tuns.md
+++ b/posts/tuns.md
@@ -16,6 +16,7 @@ An `ngrok` alternative using just SSH.
 - Host public tcp services on `localhost`
 - Share your local webserver privately with another user
 - Managed [sish](https://docs.ssi.sh) service
+- Multi-region support
 
 Using SSH tunnels, we can forward requests to your localhost from https, wss,
 and tcp.
@@ -57,6 +58,16 @@ ssh -R dev:80:localhost:8000 tuns.sh
 # now anyone can access it at https://{user}-dev.tuns.sh
 ```
 
+# Regions
+
+> tuns.sh is a global service!
+
+We do **not** have geographical-based routing for tuns.sh, so users have to pick
+the service location that best fits their needs.
+
+See our [regions page](/regions) to learn more about our geographical service
+coverage.
+
 # User namespace
 
 When creating a tunnel to `tuns` we always prefix the name with your username: