-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Setup improvements - Preflight #1473
Conversation
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 rate it! Maybe also we should check if SECRET_KEY
is left default if they choose that this is a production instance? Not sure about the security implications of this.
I think "running in |
@Twixes my understanding is that many users forget to change the default secret key and this could potentially catch quite a few of those users if we are explicit about it. |
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.
Just some UX thoughts.
@ungless Non-DEBUG instances now fail on start attempt if SECRET_KEY is set to the default, so that should cover it. |
@Twixes I see! That works great then |
I made some UI changes, take a look @paolodamico and say if anything's out of place. Definitely better on mobile now, though still not perfect. |
Changes
/_preflight/
which returns a JSON response indicating whether Django server, Redis & the database are available and ready for usage.Additional notes:
/preflight
is currently the only route from the frontend that is allowed to be accessed without being authenticated (special handling on both the backend and frontend required).Checklist