-
Notifications
You must be signed in to change notification settings - Fork 8.8k
DEV: Allow new instances to be set up directly with Discourse ID #36731
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
base: main
Are you sure you want to change the base?
Conversation
| def visit_index | ||
| visit("/finish-installation") | ||
| def has_discourse_id_button? | ||
| page.has_css?(".finish-installation__discourse-id", text: "Login with Discourse ID") |
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.
Should the "text:" use I18n instead?
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 think it's clearer without I18n personally... we use both in core afaik.
|
I think I addressed you main comments here @ZogStriP, can you give this another look. |
This relies on discourse/discourse_docker#1010
When email setup is skipped, we can register the site for Discourse ID. That means the admin (and other users), can signup/login without the site having working email at all. The goal of this feature is to simplify bootstrapping a test site. A well-functioning community will likely need working email at some point, this simplifies the first step of getting started.
Screenshot when ID auth is available:
Screenshots when setup cannot continue: