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
If production mode is the default then we should instead have a DEVELOPMENT environment variable that enables permissive CORS headers.
The PRODUCTION variable means nothing to uvicorn and it means nothing to FastAPI, we are the only ones using it. Unless there is some dark Heroku magic involved? But even then, why would it be production mode if (a) PRODUCTION is unset, or if (b) PRODUCTION is set to something truthy?
The text was updated successfully, but these errors were encountered:
instead of the confusing PRODUCTION= you now do DEVELOPMENT=1 (or
anything else truthy), and you can also explicitly specify the
deployed origin URL with ORIGIN if you like for production mode
(fixes#146)
instead of the confusing PRODUCTION= you now do DEVELOPMENT=1 (or
anything else truthy), and you can also explicitly specify the
deployed origin URL with ORIGIN if you like for production mode
(fixes#146)
The way of telling the web API to go into development mode makes no sense:
If production mode is the default then we should instead have a
DEVELOPMENT
environment variable that enables permissive CORS headers.The
PRODUCTION
variable means nothing to uvicorn and it means nothing to FastAPI, we are the only ones using it. Unless there is some dark Heroku magic involved? But even then, why would it be production mode if (a)PRODUCTION
is unset, or if (b)PRODUCTION
is set to something truthy?The text was updated successfully, but these errors were encountered: