docs
created pr with
42.1
added 42.2
1: d1a7089 ! 1: 786b48a docs: global docs
added 42.3
-: ------- > 1: 1e37996 docs: global docs
-: ------- > 2: 4a7df87 changes
1: 786b48a ! 3: a2f41f6 changes
added 42.4
1: 1e37996 < -: ------- docs: global docs
3: a2f41f6 ! 1: 4b2c45c docs: global docs
2: 4a7df87 < -: ------- changes
cmds
checkout latest patchset:
ssh pr.pico.sh print 42 | git am -3checkout any patchset in a patch request:
ssh pr.pico.sh print 42.[rev] | git am -3add changes to patch request:
git format-patch main --stdout | ssh pr.pico.sh pr add 42
Patchset
42.3
docs: global docs
Eric Bower
2025-01-13T01:23:45ZSemantic diff summary
0 added,
1 modified,
0 signature changed,
0 removed
across 1 analyzed file
(3 files skipped: unsupported file type)
+5
-0
main.go
#
+2
-3
posts/pgs.md
#
| ... | ... | @@ -507,9 +507,8 @@ In case of issues, you can manually clear the server-side cache with | |
| 507 | 507 | ||
| 508 | 508 | # Does pages have a CDN or multi-region support? | |
| 509 | 509 | ||
| 510 | - | At this point in time, we are able to serve content from a single VM. If this | |
| 511 | - | service gains traction we will commit to having a CDN with multiple regions in | |
| 512 | - | the US and EU. | |
| 510 | + | Yes, we run pages in multiple regions, internationally. See our | |
| 511 | + | [regions page](/regions) to learn more. | |
| 513 | 512 | ||
| 514 | 513 | # Removing a project | |
| 515 | 514 |
+22
-0
posts/regions.md
#
| ... | ... | @@ -0,0 +1,22 @@ | |
| 1 | + | --- | |
| 2 | + | title: Regions | |
| 3 | + | description: Where are our services located? | |
| 4 | + | keywords: [pico, services, pgs, tuns] | |
| 5 | + | toc: 1 | |
| 6 | + | --- | |
| 7 | + | ||
| 8 | + | - Ashburn, Virginia ([oci](https://cloud.oracle.com)) | |
| 9 | + | - Amsterdam, Netherlands ([netcup](https://www.netcup.com)) | |
| 10 | + | ||
| 11 | + | # Service Locations | |
| 12 | + | ||
| 13 | + | - pgs.sh (us, eu) | |
| 14 | + | - tuns.sh (us) | |
| 15 | + | - eu.tuns.sh (eu) | |
| 16 | + | - pipe.pico.sh (us) | |
| 17 | + | - prose.sh (us) | |
| 18 | + | - pastes.sh (us) | |
| 19 | + | - feeds.pico.sh (us) | |
| 20 | + | ||
| 21 | + | As demand for our services increases we will increase our service location | |
| 22 | + | coverage. |
+13
-0
posts/tuns.md
#
| ... | ... | @@ -57,6 +57,19 @@ ssh -R dev:80:localhost:8000 tuns.sh | |
| 57 | 57 | # now anyone can access it at https://{user}-dev.tuns.sh | |
| 58 | 58 | ``` | |
| 59 | 59 | ||
| 60 | + | # Regions | |
| 61 | + | ||
| 62 | + | We do **not** have geographical-based routing for tuns.sh. | |
| 63 | + | ||
| 64 | + | However, we do provide a way for users to pick a server location. With that we | |
| 65 | + | have a couple options: | |
| 66 | + | ||
| 67 | + | - tuns.sh (us, virginia) | |
| 68 | + | - eu.tuns.sh (eu, amsterdam) | |
| 69 | + | ||
| 70 | + | As usage and demand increases we will add more regions. See [regions](/regions) | |
| 71 | + | for our official list. | |
| 72 | + | ||
| 60 | 73 | # User namespace | |
| 61 | 74 | ||
| 62 | 75 | When creating a tunnel to `tuns` we always prefix the name with your username: |