Auto set DOMAIN env vars #22
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
As of 1.4, it's required to set the DOMAIN env vars or else you'll get an error when trying to browse to the Appwrite Console. This uses the GITPOD_WORKSPACE_URL env var to set the DOMAIN env vars.
TorstenDittmann
approved these changes
Sep 4, 2023
This was referenced Oct 1, 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.
What does this PR do?
As of 1.4, it's required to set the DOMAIN env vars or else you'll get an error when trying to browse to the Appwrite Console. This uses the GITPOD_WORKSPACE_URL env var to set the DOMAIN env vars.
Test Plan
I tested by spinning up gitpod and I was able to reach the Appwrite console since the .env was automatically updated.
Related PRs and Issues
None
Have you read the Contributing Guidelines on issues?
Yes