the environment should already be loaded #3
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
…ing the file directly in the plugin breaks it for all environments where the environment variables might actually come from the environment (for example: with it being loaded here the plugin wont run in docker, unless you bring your .env file into the container (bad practice))
lilbishie
approved these changes
May 9, 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.
the environment variables should already be bootstrapped by auto-gpts own runtime.
Using the file directly in the plugin breaks it for all environments where the environment variables might actually come from the environment (for example: with it being loaded here the plugin won't run in docker unless you bring your .env file into the container (bad practice))