Skip to content

Pass WalletConnect project ID to frontend dev build#579

Closed
bussyjd wants to merge 1 commit into
mainfrom
fix/walletconnect-build-arg
Closed

Pass WalletConnect project ID to frontend dev build#579
bussyjd wants to merge 1 commit into
mainfrom
fix/walletconnect-build-arg

Conversation

@bussyjd
Copy link
Copy Markdown
Collaborator

@bussyjd bussyjd commented Jun 1, 2026

Summary

  • Pass NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID as a Docker build arg for local frontend dev images.
  • Resolve the ID from NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID, WALLET_CONNECT_PROJECT_ID, or the frontend repo .env.local.
  • Keep the actual project ID out of tracked files while still baking WalletConnect into the Next.js client bundle at build time.

Validation

  • just --summary
  • FRONTEND_DIR=/Users/bussyjd/Development/Obol_Workbench/obol-stack-front-end just --dry-run dev-frontend
  • Rebuilt and pushed localhost:54103/obol-stack-front-end:dev@sha256:31798e9df946eb9836ddb93e718f08fe3f2a898c09c5ef8c807cfcbeeab16d3b locally.
  • Rolled out the local obol-frontend deployment through k3d kubectl.
  • Verified http://obol.stack:8080/marketplace renders Connect Wallet.

@OisinKyne OisinKyne force-pushed the fix/walletconnect-build-arg branch from 601c57e to 70b4735 Compare June 2, 2026 13:06
@OisinKyne
Copy link
Copy Markdown
Contributor

Where do we get this ID from, what's it for, and how does a normal user use it?

@bussyjd
Copy link
Copy Markdown
Collaborator Author

bussyjd commented Jun 3, 2026

Where do we get this ID from, what's it for, and how does a normal user use it?

This ID must be included in our frontend code so browsers can talk to the WalletConnect network, it is public by default.

@bussyjd bussyjd requested a review from OisinKyne June 3, 2026 10:32
@OisinKyne
Copy link
Copy Markdown
Contributor

We'll just inject this in the front-end image build

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.

2 participants