-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
feat(docs): Add page discussing environment variables #10
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Environment variables and secrets are not interchangeable names. A project secret has its value as any string hover you cannot view it after creation and they are set per project. Environment variables are editable and viewable. They can be any string in addition to a secret ie a secret can be used as an environment variable value. |
cobol 👍 |
Gotcha. Will update my PR to include this differentiation. Anything else? |
Replace hop deploy --env TOKEN="${env.TOKEN}" to just hop deploy --env TOKEN=VALUE since that caught my eye mostly. |
Would it be possible to add some more information under "Usage with API" — perhaps it would be easier to change to an example with the JS SDK |
While there is already documentation around project secrets, I could not find anything about environment variables and their distinguishing features versus project secrets. This copy is essentially edited around the project secrets doc page, and might be better off merging variables as a whole into one doc page.