-
Notifications
You must be signed in to change notification settings - Fork 881
Add a registration/set-up page for new admins #3225
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
Comments
I think this issue is maybe not blocked by #3223 but related to it. Is that right? |
I also think this is a 5, because of testing. Is it ok if I change it? |
@BrunoQuaresma fine to change the estimate! I was thinking it was blocked because the other ticket handles detection of whether the first user has been created, which is needed for this. |
Ahh I see, the detection is done in the API already so no need to have a blocker. |
The API call exists, but it isn't called in the frontend yet, right? If you want to just do them both together, you can skip the part about writing about the CLI. The idea was just that it's urgent to make it more clear, and #3223 was enough to do that. It's less urgent to get the full fix in (this ticket). |
Problem
Admins of new deployments can only set up their first user through the CLI
Solution
In a deployment with no users, the login page redirects to a setup page that has a UI for the setup process
Definition of Done
Notes
Here's what the signup flow looks like from the CLI: https://asciinema.org/a/cy8QVTPwazDAV6cxcV6DF1Qnj
Here's where initial user creation is implemented in the CLI: https://github.com/coder/coder/blob/v0.8.1/cli/login.go#L81-L196
The text was updated successfully, but these errors were encountered: