Add public nostr submission relay and approved-content sync #705
No files matched your search
@@ -91,9 +91,10 @@ ruby site-cookbooks/kosmos_strfry/test/strfry_sync_conf_test.rb
|
||||
`curl -fsSI https://gitea.kosmos.org/kosmos/akkounts/raw/branch/live/extras/strfry/submission-policy.mjs`
|
||||
and the same for `sync-policy.mjs`. These files are produced by WS1, not by
|
||||
this repo.
|
||||
1. **DNS (manual).** Add an **A/AAAA record** for `submit.nostr.kosmos.org` at
|
||||
Gandi pointing at the openresty proxy node(s). Chef does not manage DNS, and
|
||||
the `gandi_dns` Let's Encrypt challenge cannot succeed without it.
|
||||
1. **DNS.** `submit.nostr.kosmos.org` is a **CNAME to `lb.kosmos.org`** at Gandi
|
||||
(already configured). Chef does not manage DNS; the `gandi_dns` Let's Encrypt
|
||||
challenge cannot succeed without it. Verify it resolves before converging the
|
||||
proxy nodes.
|
||||
2. **Relay node.** Assign `role[strfry_submission]`, converge. Creates the
|
||||
binary (or reuses it), DB, config, policy and `strfry-submission.service`.
|
||||
The firewall allow-lists the current `role:openresty_proxy` node IPs, so the
|
||||
@@ -111,6 +112,18 @@ ruby site-cookbooks/kosmos_strfry/test/strfry_sync_conf_test.rb
|
||||
* `journalctl -u strfry-sync` shows accepted events after an approval.
|
||||
* The production relay's NIP-11 and `_strfry` upstream are unchanged.
|
||||
|
||||
## Pre-go-live verification
|
||||
|
||||
* **LMDB concurrency (verified 2026-11-17 on the nuc's `:7777` mirror).** A
|
||||
`strfry sync --dir down` was run against the same LMDB that the live relay was
|
||||
serving from. Result: sync exited 0 and the relay answered 13/13 subscriptions
|
||||
(39 events) during the sync; the relay stayed active and the event count was
|
||||
unchanged. This is the same access pattern the approved-sync uses on strfry-1
|
||||
(same DB, separate `strfry sync` process), so no additional lock is needed.
|
||||
* **No rogue sync path.** Before enabling the timer, confirm that no external
|
||||
negentropy/websocket path can produce `sourceType = "Sync"` on the production
|
||||
relay; the sync policy is fail-closed on the exact staging URL.
|
||||
|
||||
## Rollback
|
||||
|
||||
* **Sync:** set `strfry.approved_sync.enabled = false` and converge, then
|
||||
|
||||
@@ -65,9 +65,10 @@ verify those services do not depend on Node 14 before converging — see
|
||||
|
||||
## Deployment
|
||||
|
||||
1. Manual DNS: add an A/AAAA record for `submit.nostr.kosmos.org` at Gandi
|
||||
pointing at the openresty proxy node(s). **Chef does not manage DNS**, and the
|
||||
Let's Encrypt certificate cannot be issued without it.
|
||||
1. DNS: `submit.nostr.kosmos.org` is a **CNAME to `lb.kosmos.org`** (the
|
||||
openresty proxy load balancer) at Gandi. **Chef does not manage DNS**, and the
|
||||
Let's Encrypt certificate cannot be issued without it. The CNAME is already in
|
||||
place; verify it resolves before converging the proxy nodes.
|
||||
2. Provision/assign `role[strfry_submission]` and converge the relay node.
|
||||
3. Converge the openresty proxy nodes (`role[openresty_proxy]`), which adds the
|
||||
`kosmos_strfry_submission::nginx` site.
|
||||
|
||||
Reference in new issue
Block a user