Skip to content
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.

binder warning #300

Merged
merged 2 commits into from
Oct 7, 2018
Merged

binder warning #300

merged 2 commits into from
Oct 7, 2018

Conversation

jaygambetta
Copy link
Member

@jaygambetta jaygambetta commented Oct 6, 2018

Fixes #231 by putting in the readme a warning about the binder

@jaygambetta jaygambetta changed the title Fixes #231 binder warning Oct 6, 2018
@jaygambetta jaygambetta requested review from nonhermitian, diego-plan9 and ajavadia and removed request for nonhermitian October 6, 2018 23:39
Copy link
Contributor

@nonhermitian nonhermitian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally do not like having the Binder route as the highlighted way to run the notebooks. I would prefer to say run the notebooks locally is the default, and in the end best way to go. The binder is really to get started quickly, but the need to regenerate your token [which itself is hidden under the 'advanced' tab in your account (maybe should be easier to get)] really is not ideal. Perhaps we have a Binder image that has fewer tutorials that only rely on Aer, and then say you need to run locally to get hardware access?

Anyway, just my thoughts, this PR looks good.

@quantumjim
Copy link
Member

There could also be the route of setting up our own server for Binder or jupyterhub, to allow the easy access option without the security issues. I'll look into it for the future.

@nonhermitian
Copy link
Contributor

I also brought that up a while ago and, at least at the time, it was deemed too much work.

@jaygambetta
Copy link
Member Author

We can change order. @quantumjim don’t waste too much time as others are looking into this as we speak.

@jaygambetta jaygambetta merged commit f14787e into Qiskit:master Oct 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants