puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-10-14 13:22:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix the Tailscale Serve command and log rotation defaults (#6284)

Browse Source 
The web UI guide gave the pre-1.52 `tailscale serve https / <target>`
form, which current Tailscale rejects with "invalid number of
arguments". The configuration page said logs keep 2 files in total,
while the daemon keeps 3 rotated files next to the active one.

Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
This commit is contained in:
paseo-bot[bot]
2026-10-07 09:51:17 +02:00
committed by GitHub
parent f13bb2136c
commit 28f7528588
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/configuration.md
+2 -2
View File
@@ -141,7 +141,7 @@ Daemon logging uses separate console and file sinks by default:
- Console: `info` and above
- File (`$PASEO_HOME/daemon.log`): `trace` and above
- File rotation: `10m` max file size, `2` retained files total (active + 1 rotated)
- File rotation: `10m` max file size, `3` rotated files kept alongside the active file
```json
{
@@ -155,7 +155,7 @@ Daemon logging uses separate console and file sinks by default:
"path": "daemon.log",
"rotate": {
"maxSize": "10m",
"maxFiles": 2
"maxFiles": 3
}
}
}
public-docs/web-ui.md
+1 -1
View File
@@ -197,7 +197,7 @@ If you don't want to manage a reverse proxy or open ports, a tunnel gives you an
- **Tailscale Serve** keeps it inside your tailnet, no public exposure, TLS handled for you:
```bash
tailscale serve https / http://127.0.0.1:6767
tailscale serve --bg http://127.0.0.1:6767
```
Reach it at `https://<your-machine>.<tailnet>.ts.net/`. Only devices on your tailnet can connect.