Files
observer/asset/nginx/blackbeard.internal.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

61 lines
2.1 KiB
Plaintext

# Mesh vhost for blackbeard.observer, on the oolon edge proxy (kosherinata).
#
# This exists because a public name does not hairpin: from inside the mesh,
# `blackbeard.observer` resolves to the site's WAN address, the packet hits the
# OPNsense LAN interface, and the connection dead-ends
# (architecture/reverse-proxies.md §2). Mesh clients use this name instead.
#
# Cert: internal `lair` CA, renewed by step@blackbeard.timer
# (architecture/internal-tls.md). Same webroot and same upstream as the public
# vhost — only the name and the certificate differ.
#
# ln -sf ../sites-available/blackbeard.internal.conf /etc/nginx/sites-enabled/
#
# The split-horizon DNS record is a separate manual step on BOTH site routers:
# opn-cli --config ~/.opn-cli/{hanzalova,kosherinata}.yml unbound host create \
# --hostname blackbeard --domain internal --rr A --server <oolon mesh ip>
# A record added to only one router NXDOMAINs everywhere else.
server {
listen 127.0.0.1:14443 ssl proxy_protocol;
http2 on;
server_name blackbeard.internal;
ssl_certificate /etc/nginx/tls/cert/blackbeard.internal.pem;
ssl_certificate_key /etc/nginx/tls/key/blackbeard.internal.pem;
ssl_protocols TLSv1.3;
ssl_trusted_certificate /etc/pki/ca-trust/source/anchors/root-internal.pem;
absolute_redirect off;
root /var/www/blackbeard.observer;
index index.html;
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;
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;
proxy_read_timeout 3600s;
proxy_send_timeout 3600s;
proxy_buffering off;
}
}