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

Select which Tessel to use #93

Closed
Frijol opened this issue May 5, 2015 · 10 comments
Closed

Select which Tessel to use #93

Frijol opened this issue May 5, 2015 · 10 comments

Comments

@Frijol
Copy link
Member

@Frijol Frijol commented May 5, 2015

From comments on the T2 CLI spec.
The CLI should select a tessel based on this list in order of priority:

  1. using the --name flag
  2. an environment variable in the terminal, set as export TESSEL=Bulbasaur
  3. if there is a single tessel connected over USB, prefer that one
  4. if there is only one tessel visible, use that one

Meta:

  • document this selection process
@Frijol Frijol added the spec-cli label May 5, 2015
@Frijol

This comment has been minimized.

Copy link
Member Author

@Frijol Frijol commented May 5, 2015

@nplus11

This comment has been minimized.

Copy link
Contributor

@nplus11 nplus11 commented May 5, 2015

The config file is under debate here: #94

@johnnyman727

This comment has been minimized.

Copy link
Contributor

@johnnyman727 johnnyman727 commented May 5, 2015

[Cross posting from #93]

I still think this is a bad idea. Folks would have to look up how to select a particular Tessel anyway so showing them how to set an environment variable is just as much effort (but more useful down the road).

I have rarely seen people want to set a project to a specific Tessel. This could cause confusion if they ever try to do a demo with a different Tessel than they built the project with.

In addition, project configuration files already exist (like package.json) and adding another file is more of a headache.

@nplus11

This comment has been minimized.

Copy link
Contributor

@nplus11 nplus11 commented May 5, 2015

I agree. I think we need a clear picture of env vars rather than project mapped tessels

@johnnyman727

This comment has been minimized.

Copy link
Contributor

@johnnyman727 johnnyman727 commented Jun 5, 2015

Any more opinions on this or should I close it? @Frijol

@Frijol

This comment has been minimized.

Copy link
Member Author

@Frijol Frijol commented Jun 5, 2015

I think the listing in the top comment is correct– unless there was a decision re config files that changes that?

Is the listed order implemented in code?

@johnnyman727

This comment has been minimized.

Copy link
Contributor

@johnnyman727 johnnyman727 commented Jun 5, 2015

I feel strongly that there should be no config file option for the reasons listed in my comment from May 5.

@johnnyman727

This comment has been minimized.

Copy link
Contributor

@johnnyman727 johnnyman727 commented Jun 6, 2015

@Frijol if there are no other opinions on this, I think we should remove the config file option. Sound good?

@Frijol

This comment has been minimized.

Copy link
Member Author

@Frijol Frijol commented Jun 6, 2015

Sure, removing now.

@johnnyman727

This comment has been minimized.

Copy link
Contributor

@johnnyman727 johnnyman727 commented Jun 7, 2015

Partially fixed with #151. We just need to implement the selection mechanism if you have multiple USB or LAN Tessels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.