Files
observer/asset/nginx/blackbeard.observer.conf
T
grenadeandClaude Opus 5 5f3aac2a13
deploy / build (push) Failing after 5s
deploy / deploy-api (push) Has been skipped
deploy / deploy-web (push) Has been skipped
feat(chains): discover every Quantus chain from telemetry; track the ones we can reach
The chain list is no longer config. substrate-telemetry announces every chain it
knows — with live node counts — before and independent of any subscription, so
one feed connection that never subscribes is a complete, self-maintaining index.
A chain that launches tomorrow appears in the nav on its own.

Config now contributes only RPC endpoints. Authorship lives in the `pow_` digest
of a block *header*, and telemetry publishes hashes and heights but never
headers — so a chain with no endpoint is listed with its node count and is not
navigable, and the nav says why rather than offering an empty board. The two
sets join on genesis hash, never on name.

Two chains are tracked in full: Planck (our own node on bob) and Heisenberg
(a1-heisenberg.quantus.cat, found via Quantus-Network/quantus-apps). Both decode
identically — same digest shape, same QPoW runtime API — which is the proof that
adding a chain is one [[chains]] entry and no new code. Quantus Staging Mainnet
and Quantus Dirac Testnet are listed and disabled: no endpoint exists under the
a1-/a2- pattern and none resolves under any plausible name.

Nav is ordered by node count descending, ties broken on id so it cannot reshuffle
between refreshes.

Telemetry now also yields chain-wide best height, best finalized height, average
block time and the client-version histogram (feed codes 1, 2, 12 and 22).

Infra moves to a single site: oolon fronts blackbeard.observer, reverse-proxying
cross-site over the mesh to the API beside the node on bob. That hop is the one
the loopback health probe cannot see, so the deploy now checks it explicitly —
a firewalld service scoped to bob's own /16 would leave a live site with a dead
/v1 and nothing would fail. infra-setup gains `dns` and `cert` roles that run on
oolon with the credential already there: the Cloudflare token is never copied off
the proxy, and it refuses to repoint an apex record that already exists.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSDYiibCtELsrjQq6KXnoi
2026-09-04 13:04:11 +03:00

97 lines
4.2 KiB
Plaintext

# Public vhost for blackbeard.observer, on the oolon edge proxy (kosherinata).
#
# Cert: Let's Encrypt via certbot + Cloudflare DNS-01 (architecture/external-tls.md).
# Installed by script/infra-setup.sh --edge, never by CI — the runner has no
# rights to read certificate keys or reload nginx on a shared edge proxy.
#
# ln -sf ../sites-available/blackbeard.observer.conf /etc/nginx/sites-enabled/
#
# listen 127.0.0.1:14443 + proxy_protocol, NOT 443: an nginx stream SNI router
# owns TCP 443 on this host and hands every non-passthrough name to the local
# https tier (architecture/reverse-proxies.md §5). Binding 443 here double-binds
# the port across http{} and stream{} — `nginx -t` cannot detect it, and the
# failure mode is nginx silently serving stale certificates. Copy this listen
# line from a currently ENABLED vhost; several files in sites-available have
# drifted from their enabled counterparts.
#
# NOTE: the upstream is CROSS-SITE. oolon is at kosherinata; the API runs on bob
# at hanzalova, because that is where the Planck node it reads lives. The hop
# traverses the WireGuard mesh, so the API's firewalld service must be open to
# the whole default zone rather than scoped to bob's own /16 — a rich rule
# scoped the way quantus-node's RPC is would reject oolon and the site would
# serve a static bundle with a dead /v1.
# The `blackbeard_api` upstream is declared once in
# conf.d/blackbeard-upstream.conf so both vhosts can use it independently, and
# `$connection_upgrade` comes from the proxy's existing conf.d map — the same
# one lair/quantus's vhost relies on. Both are installed by infra-setup.sh.
server {
listen 127.0.0.1:14443 ssl proxy_protocol;
http2 on;
server_name blackbeard.observer;
ssl_certificate /etc/letsencrypt/live/blackbeard.observer/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/blackbeard.observer/privkey.pem;
# TLS 1.2 stays enabled here, unlike the .internal vhost: this is a public
# site and its audience is not a controlled fleet.
ssl_protocols TLSv1.2 TLSv1.3;
# The vhost believes it is serving 127.0.0.1:14443, so any redirect it
# generates itself carries that port and is unreachable. Latent for a pure
# SPA, but one real directory under the webroot would break every URL
# without a trailing slash (reverse-proxies.md §4).
absolute_redirect off;
root /var/www/blackbeard.observer;
index index.html;
# The built SPA. Hashed asset filenames are immutable; index.html must not
# be cached or a deploy would leave browsers loading a bundle that no longer
# exists.
location / {
try_files $uri $uri/ /index.html;
}
location /assets/ {
expires 1y;
add_header Cache-Control "public, immutable";
}
location = /index.html {
add_header Cache-Control "no-cache";
}
location /v1/ {
proxy_pass http://blackbeard_api;
proxy_http_version 1.1;
# The WebSocket upgrade. Without these three lines the socket silently
# falls back to a plain request that hangs, and the page shows
# "reconnecting" forever with nothing in any log.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# A chain can be quiet for a minute at a time and a browser tab can sit
# open all day. The 60s default would cut every socket mid-session and
# surface as an unexplained disconnect.
proxy_read_timeout 3600s;
proxy_send_timeout 3600s;
# Buffering an endless stream is exactly wrong: it would hold each
# message until a buffer filled, which on a quiet chain is minutes.
proxy_buffering off;
}
# Public, read-only, entirely derived from public block headers. No auth,
# nothing to leak; documented here so the absence is deliberate rather than
# an oversight.
add_header X-Content-Type-Options nosniff always;
add_header Referrer-Policy same-origin always;
}