Normalize backend environment variables #678
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pshenmic
requested changes
Sep 9, 2025
Owner
pshenmic
left a comment
pshenmic
left a comment
There was a problem hiding this comment.
Postgres envs between indexer and api also differntiate
Collaborator
Author
Same. Difference only in POSTGRES_PORT, which optional for connection and you can also specify this variable for API 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
We need to normalize backend env format
Things done
Since, in addition to the API, we also have an indexer that uses some of the same endpoints, we will change the names of the variables. We also have a very outdated readme file in terms of environment variables.
DASHCORE_*toCORE_RPC_*