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

Direct users away from Blockstack CLI #345

Closed
jackzampolin opened this Issue Sep 11, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@jackzampolin
Copy link
Contributor

jackzampolin commented Sep 11, 2017

This is an issue derived from a forum post by @larrysalibra. We are trying to direct users away from the CLI. I think changing the following places on the site/github would be a good fix:

  • Core README
    • Remove apt install instructions: blockstack/blockstack-core#595
    • Add a warning to the top that if you are looking to register a name or use Blockstack applications then you need to download browser.
  • /install on blockstack.org
    • Remove the Core Server + CLI section and replace it with a Full Node section.
  • /tutorials
    • Remove link to the CLI Basics tutorial

This seems like most of the references. Anyone see any other ones? @larrysalibra @kantai @muneeb-ali @jcnelson?

@kantai

This comment has been minimized.

Copy link
Member

kantai commented Sep 11, 2017

We need to explain to users how to run and configure the blockstack-browser + blockstack-core pairing in Linux and Windows without engaging with the blockstack api X CLI.

I think that the docker launcher is the easiest way for them. It will require an additional password entry over the macOS install.

@jackzampolin

This comment has been minimized.

Copy link
Contributor

jackzampolin commented Sep 11, 2017

@kantai Does that mean adding protocol handlers for Linux and Mac, or a more detailed writeup on where the configuration lives for each of the parts?

I think @jcnelson had some info on the Linux one in this issue:
blockstack/blockstack-browser#324

@kantai

This comment has been minimized.

Copy link
Member

kantai commented Sep 12, 2017

The protocol handler in Linux just needs a little attention. There's an example file and some instructions here:

https://github.com/blockstack/blockstack-core/blob/master/docs/setup_core_portal.md#setting-up-a-protocol-handler

We should document it better and script it for users.

The Windows installer currently sets up the protocol handler for port 8888 and it works well.

The macOS app sets the protocol handler well also.

I think, bigger than this is just testing the functionality of the docker distribution. The apt issue in core affects the docker containers, but it isn't apparent until you try to initialize storage by signing into apps. (Integration tests would be nice, but the logging into Dropbox aspect makes it kind of tricky to script).

@jackzampolin

This comment has been minimized.

Copy link
Contributor

jackzampolin commented Sep 14, 2017

Open PR's that need review 👀 :

What I'm missing the browser README update

@jackzampolin

This comment has been minimized.

Copy link
Contributor

jackzampolin commented Jan 10, 2018

Merged!

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