Skip to content

Promote synvya-staging to production - #65

Merged
alejandro-runner merged 6 commits into
synvyafrom
synvya-staging
May 14, 2026
Merged

Promote synvya-staging to production#65
alejandro-runner merged 6 commits into
synvyafrom
synvya-staging

Conversation

@alejandro-runner

Copy link
Copy Markdown
Member

Summary

  • Configure per-environment Nostr relay URLs (staging vs production)
  • Use only wss://relay.synvya.com for production relay
  • Fix admin team-lookup to match teams by stored-key pubkey

Test plan

  • Verify relay configuration is correct for production environment
  • Confirm team lookup by pubkey works after deploy
  • Smoke-test NIP-46 signing through production relay

🤖 Generated with Claude Code

alejandro-runner and others added 6 commits May 13, 2026 08:59
Move BUNKER_RELAYS, VITE_NDK_EXPLICIT_RELAYS, and VITE_NDK_BUNKER_RELAYS
into per-environment blocks in load-secrets.sh. Update .env.example
defaults for local Synvya dev.

Staging: wss://relay.staging.synvya.com
Production: wss://relay.damus.io, wss://nos.lol, wss://relay.synvya.com
Local: wss://relay.local.synvya.com

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Configure per-environment Nostr relay URLs
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use only wss://relay.synvya.com for production
The CLI's `synvya delete` passes the restaurant's hex pubkey to
`/api/admin/team-lookup`, but the query only searched `t.name ILIKE`.
Add an `OR EXISTS` clause so an exact stored-key pubkey match also
returns the owning team.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix(core): match teams by stored-key pubkey in admin team-lookup
@alejandro-runner
alejandro-runner merged commit 20a9c92 into synvya May 14, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant