Configure Postgres with separate env variables #108
Merged
Conversation
This file contains 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
amritghimire
previously approved these changes
Jun 19, 2023
…stgres url feature
|
I bumped the Studio version to v2.4.0 |
Studio v2 Bumped the django version to v4
mjasion
approved these changes
Jun 21, 2023
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.
Some users may want to use Postgres variables with certain symbols such as
@in them. Unfortunately, this breaks the Postgres connection URI, as certain symbols get treated as delimiters.To work around it, I've refactored the values and environment passed to Studio so that we always use separate environment variables for the Postgres configuration. This means that the previous fields:
global.postgres.databaseUrlglobal.postgres.databaseUserglobal.postgres.databasePasswordare now deprecated.