docs

created pr with 42.1 on 2025-01-13T01:24:09Z · by c8ef7d19

added 42.2 on 2025-01-13T01:25:24Z · by c8ef7d19


                      1:  d1a7089 ! 1:  786b48a docs: global docs

added 42.3 on 2025-01-24T14:31:45Z · by c8ef7d19


                      -:  ------- > 1:  1e37996 docs: global docs


                      -:  ------- > 2:  4a7df87 changes


                      1:  786b48a ! 3:  a2f41f6 changes

added 42.4 on 2025-01-24T14:32:16Z · by c8ef7d19


                      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 -3

checkout any patchset in a patch request:

ssh pr.pico.sh print 42.[rev] | git am -3

add changes to patch request:

git format-patch main --stdout | ssh pr.pico.sh pr add 42

Patchset `42.1` on 2025-01-13T01:24:09Z · commit d1a7089

→ docs: global docs

Eric Bower 2025-01-13T01:23:45Z

docs: global docs

Eric Bower 2025-01-13T01:23:45Z

Semantic diff summary

0 added, 1 modified, 0 signature changed, 0 removed across 1 analyzed file (3 files skipped: unsupported file type)

main.go

function_declaration main modified

+5 -0 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",

+12 -6 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

+22 -0 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)
- rss-to-emal (us)

As demand for our services increases we will increase our service location
coverage.

+13 -0 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:

...	...		@@ -149,6 +149,11 @@ func main() {
149	149		Href: "/faq",
150	150		Page: pager("faq.md"),
151	151		},
	152	+	{
	153	+	Text: "Regions",
	154	+	Href: "/regions",
	155	+	Page: pager("regions.md"),
	156	+	},
152	157		{
153	158		Text: "IRC",
154	159		Href: "/irc",

...	...		@@ -492,17 +492,23 @@ Then open your browser to http://localhost:1337
492	492
493	493		# Caching
494	494
495		-	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).
	495	+	To improve the page speed, pgs sites are cached for 10 minutes by default. This
	496	+	is controlled by the
	497	+	[`Cache-Control: max-age=600` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control)
	498	+	which you can [override with a `_headers` file](#headers).
496	499
497		-	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.
	500	+	There are two levels of caching: server-side and client-side. The server-side
	501	+	cache is automatically cleared every time you upload files, but client-side
	502	+	caches only expire when `max-age` seconds pass, or if you force-reload or clear
	503	+	your browser cache manually.
498	504
499		-	In case of issues, you can manually clear the server-side cache with `ssh pgs.sh cache project-name`.
	505	+	In case of issues, you can manually clear the server-side cache with
	506	+	`ssh pgs.sh cache project-name`.
500	507
501	508		# Does pages have a CDN or multi-region support?
502	509
503		-	At this point in time, we are able to serve content from a single VM. If this
504		-	service gains traction we will commit to having a CDN with multiple regions in
505		-	the US and EU.
	510	+	Yes, we run pages in multiple regions, internationally. See our
	511	+	[regions page](/regions) to learn more.
506	512
507	513		# Removing a project
508	514

...	...		@@ -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	+	- rss-to-emal (us)
	20	+
	21	+	As demand for our services increases we will increase our service location
	22	+	coverage.

...	...		@@ -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:

docs

Patchset 42.1 on 2025-01-13T01:24:09Z · commit d1a7089

Patchset `42.1` on 2025-01-13T01:24:09Z · commit d1a7089