Skip to content
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

Add first use screen #26

Closed
monkeydom opened this issue Apr 4, 2019 · 2 comments
Closed

Add first use screen #26

monkeydom opened this issue Apr 4, 2019 · 2 comments
Assignees

Comments

@monkeydom
Copy link
Collaborator

Should be used to configure what needs to be configured. E.g. at least:

  • main user account
  • smtp stuff
  • domain
  • storage options
@monkeydom
Copy link
Collaborator Author

To get a basic idea a look at the gogs first run screen might be of interest:
gogs-first-run

@monkeydom monkeydom added this to the v0.3.0 - MVP milestone Jul 28, 2019
@monkeydom monkeydom self-assigned this Sep 19, 2019
@monkeydom
Copy link
Collaborator Author

In our current deploy setup, a lot of those happen in docker container environment settings. So it'll be more likely less complete. Currently I'm thinking:

  • main admin username/password
  • minimal instance settings
    • allow non-admins to create networks
    • allow sign-up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants