-
Notifications
You must be signed in to change notification settings - Fork 14k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: docker compose refusing to start #24565
Conversation
docker/docker-bootstrap.sh
Outdated
@@ -46,7 +46,7 @@ case "${1}" in | |||
celery --app=superset.tasks.celery_app:app beat --pidfile /tmp/celerybeat.pid -l INFO -s "${SUPERSET_HOME}"/celerybeat-schedule | |||
;; | |||
app) | |||
echo "Starting web app..." | |||
echo "Starting web app on debug..." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm probably missing something, but isn't this conditional on FLASK_DEBUG
being set to true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, but there's the debugger and the debug on flask
"The debugger is enabled by default when the development server is run in debug mode."
adding "debug" here is not correct, I want to differentiate between starting with Flask or gunicorn
Insightful |
SUMMARY
Currently
docker-compose up
is refusing to start since debug is not enabled anymore.We now use
FLASK_DEBUG=true
sinceFLASK_ENV
is deprecatedThis is a small fix for it
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION