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

Warning screen about missing plugin on console landing #2155

Open
akarasulu opened this issue Nov 28, 2017 · 0 comments
Open

Warning screen about missing plugin on console landing #2155

akarasulu opened this issue Nov 28, 2017 · 0 comments

Comments

@akarasulu
Copy link
Contributor

Situation

I would like to make installation and user guidance through that process uber simple. I need some help from our console to achieve this. That said, here are a couple facts about the console and about using the system that must be satisfied:

  • The browser plugin just has to be installed no matter what.
  • The browser plugin has to have at least one PGP key pair.

These should happen before even login into the console occurs. Up to now we are writing and telling the user you have to do this before using the product and its just not working. Instead, we need the machines to guide the user.

Proposal

  1. Before logging in the console should attempt to detect the presence of the browser plugin, if not present then it should give a nice noticeable graphic with a click here to get the plugin. This link should take the user directly to the store to get the plugin.
  2. Again before logging in, the console should attempt to detect if the user has at least one key pair installed in the plugin. If not we show a page and ask the user to generate or import a key pair. We should offer a button / link to go to the 'options' dialog of the browser plugin and have it prompt for generating or importing a key.

Once these two requirements are satisfied the user should be able to login into the Subutai Console.

Other Things

After provisioning a peer, the Vagrant boxes will be made to directly launch to the console URL whatever port it runs on. Then the user can interact there instead of reading directions about next steps from the CLI. We're going to stop writing directions. No one follows them.

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

No branches or pull requests

4 participants