You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "settings.py", line 8, in<module>
ENV = env.str('ENV')
File "/.../venv/lib/python3.6/site-packages/environs.py", line 47, in method
'Environment variable "{}" not set'.format(proxied_key or parsed_key)
environs.EnvError: Environment variable "FLASK_ENV" not set
Is it intentional to only allow proxying variables within the prefix scope?
Obviously there are many possible workarounds to fix the error, however it feels unintuitive to restrict proxying to a prefix scope.
The text was updated successfully, but these errors were encountered:
When I proxy a non-prefixed env var to a prefixed one and try to load them an error is thrown.
Example:
.env
settings.py
Output:
Is it intentional to only allow proxying variables within the prefix scope?
Obviously there are many possible workarounds to fix the error, however it feels unintuitive to restrict proxying to a prefix scope.
The text was updated successfully, but these errors were encountered: