You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/12 01:49:51 UTC

[GitHub] [superset] cdutr commented on pull request #17984: fix: Change default SECRET_KEY, improve docs and banner warning on de…

cdutr commented on pull request #17984:
URL: https://github.com/apache/superset/pull/17984#issuecomment-1010548905


   I believe this change broke this [tutorial](https://superset.apache.org/docs/installation/installing-superset-using-docker-compose) for running Superset through Docker, running in dev mode.
   
   I was working on this [issue](https://github.com/apache/superset/issues/17076) when this MR's breaking change hit me. What do you recommend doing? Update the tutorial, suggesting running the `SECRET_KEY` update process? Or automate a bypass on that logic when in the development mode?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org