Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specifications for env inputs? #1

Open
thekidnamedkd opened this issue Jun 2, 2023 · 1 comment
Open

Specifications for env inputs? #1

thekidnamedkd opened this issue Jun 2, 2023 · 1 comment

Comments

@thekidnamedkd
Copy link

thekidnamedkd commented Jun 2, 2023 •
edited

I believe I have everything necessary for env inputs on Vercel deploy.

NEXT_PUBLIC_WC_ID -- This is a Wallet Connect project ID?
NEXT_PUBLIC_INFURA_ID -- Standard Infura API Key?
SESSION_SECRET -- this is a generated string? Like an HMAC hash? Not specific to one of the above providers?

Assuming all the above are true, I was getting a client side error initially with minimal info just using a random string for the session secret. But generating a proper HMAC hash and redeploy seemed to resolve.

I would be happy to submit a PR with more specific 'Getting Started' instructions for the README once I can confirm the best practice. :)
@thekidnamedkd
Copy link
Author

thekidnamedkd commented Jun 2, 2023 •
edited

Think I can assume SESSION_SECRET is for Connect Kit SIWE -- mostly critically just 32 characters req'd:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thekidnamedkd