dev-stack: wire nostr-transport env vars into lnbits service
Some checks are pending
ci / regtest (push) Waiting to run
Some checks are pending
ci / regtest (push) Waiting to run
Adds NOSTR_TRANSPORT_ENABLED + NOSTR_TRANSPORT_RELAYS so the nostr-native-transport branch can be exercised end-to-end out of the dev container without manual env overrides each spin-up. Points the transport at the in-container nostrrelay extension (relay id "test", which must be created once via the LNbits admin UI). The transport's reconnect loop tolerates the relay not being ready at startup — it retries every 5s — so first-time setup is just: bring up the stack, create the relay in the UI, watch the transport log "connected to ws://localhost:5001/nostrrelay/test". Pairs with branch nostr-native-transport on aiolabs/lnbits. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
b46144c551
commit
49dd96ef69
1 changed files with 8 additions and 0 deletions
|
|
@ -28,6 +28,14 @@ services:
|
|||
LNBITS_EXTENSIONS_DEFAULT_INSTALL: "lnurlp,nostrclient,nostrrelay,nostrmarket,events,libra,satmachineclient,satmachineadmin"
|
||||
LNBITS_ADMIN_EXTENSIONS: "nostrclient,nostrrelay,satmachineadmin"
|
||||
LNBITS_USER_DEFAULT_EXTENSIONS: "lnurlp,nostrmarket,events,libra,satmachineclient"
|
||||
# Nostr transport layer (HTTP-free RPC over kind-21000 events).
|
||||
# On first boot a keypair is auto-generated and logged; copy the
|
||||
# printed pubkey into your driver script. The relay points at the
|
||||
# nostrrelay extension running inside the same container — a relay
|
||||
# named "test" must be created via the UI before the transport
|
||||
# will successfully connect (the reconnect loop retries every 5s).
|
||||
NOSTR_TRANSPORT_ENABLED: "true"
|
||||
NOSTR_TRANSPORT_RELAYS: '["ws://localhost:5001/nostrrelay/test"]'
|
||||
ports:
|
||||
- 5001:5001
|
||||
volumes:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue