nixos/middleman: Serve Paseo web app ourselves

Serve the web app from the Paseo package on `paseo.nul.ie` and point
the daemon's pairing links there, so browsers no longer load Paseo's
hosted app. It connects through our relay, so the daemon stays on
loopback.

Move the patched Paseo package into the shared overlay so `middleman`
and `slop-cannon` use the same build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-16 00:39:48 +00:00
co-authored by Claude Opus 5.5
parent a62b8351fa
commit b0a7f3cd89
5 changed files with 46 additions and 14 deletions
@@ -52,6 +52,9 @@ app, in place of Paseo's hosted relay.
`paseo-relay.nul.ie`. It keeps no state, so a restart only drops connections.
- The relay can't read or forge messages, so the vhost is open to the world. Its Prometheus
`/metrics` is not exposed; `/health` and `/ready` are.
- `paseo.nul.ie` serves Paseo's web app as static files, taken from the same patched Paseo package
as the daemon. Pairing links from our daemon point there, and the app connects through the relay,
so nothing from `paseo.sh` is needed in the browser.
## Network assignments
@@ -90,6 +93,7 @@ all vhosts are `onlySSL`, kTLS and HTTP/2. "SSO" = gated behind nginx-sso (`gene
| `speed.nul.ie` | `localhost:8989` | librespeed |
| `librespeed.ams1.int.nul.ie` | `localhost:8989` | librespeed on the internal domain (internal wildcard cert) |
| `paseo-relay.nul.ie` | `localhost:4000` | Paseo relay; websockets with long timeouts; `/metrics` blocked |
| `paseo.nul.ie` | static Paseo web app | falls back to `index.html`; precompressed files served as-is |
| `md.nul.ie` | `object-ctr:3000` | HedgeDoc; websockets |
| `pb.nul.ie` | `object-ctr:8088` | wastebin |
| `photos.nul.ie` | `jackflix-ctr:2342` | PhotoPrism; websockets |
+10 -7
View File
@@ -67,18 +67,21 @@ from the app don't survive a restart. It:
### Connectivity
- The daemon listens on `127.0.0.1:6767` only. The phone app and the hosted web app at
`https://app.paseo.sh` reach it through our relay on
[`middleman`](../../../colony/shill/containers/middleman.md#paseo-relay) (`paseo-relay.nul.ie`).
- The daemon listens on `127.0.0.1:6767` only. The phone app and the browser reach it through our
relay on [`middleman`](../../../colony/shill/containers/middleman.md#paseo-relay)
(`paseo-relay.nul.ie`).
- Traffic through the relay is end-to-end encrypted between the app and the daemon; the relay sees
only addresses, timing and sizes. The pairing QR code or link is the trust anchor; treat it like a
password. Switching relays means re-pairing.
- Push notifications go from the daemon to Expo's push service (`exp.host`), one outbound request
per notification carrying its text.
- In a browser, open the link `paseo daemon pair` prints: it loads the hosted web app with our
relay's address. The daemon's own web UI is off (`features.webUi.enabled` defaults to `false`);
if enabled, it needs a secure context, so it would be reached through an SSH tunnel to
`localhost` (`ssh -L 6767:127.0.0.1:6767 slop-cannon`).
- In a browser, open the link `paseo daemon pair` prints. `app.baseUrl` points it at our copy of
the web app on `paseo.nul.ie`, served by `middleman`, instead of `app.paseo.sh`. The daemon's own
web UI stays off, so nothing needs to reach the daemon directly.
- Opening a pairing link in the address bar adds the host without asking for the daemon password,
and the host page then shows "Password required" with no way to enter it. Instead, use the app's
option to paste a pairing link, which prompts for the password; remove a host added the other way
first.
### State