[Proposal] Reboot function call

[reconbot]

I'd like to propose a tessel.reboot() function call on the tessel object. You can shell out to reboot, but that seems messy.

[rwaldron]

Reboot isn't related to port & io interaction—why not just let user code shell out to reboot?

[reconbot]

Do we want people using linux or js? We provide a bunch of tessel services
this seems reasonable to provide.

On Wed, Aug 3, 2016, 9:23 PM Rick Waldron notifications@github.com wrote:

Reboot isn't related to port & io interaction—why not just let user code
shell out to reboot?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#188 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABlbvBavexfh26ON1UKh6JoXGzkuN0Sks5qcT8DgaJpZM4JYr5B
.

[rwaldron]

Is rebooting directly from your JS code something that is frequently needed?

[reconbot]

It's something I do to my router and my nest and at least once to my drop
cam when something hasn't worked right.

On Wed, Aug 3, 2016, 9:28 PM Rick Waldron notifications@github.com wrote:

Is rebooting directly from your JS code something that is frequently
needed?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#188 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABlbgniO1BL_fpQ4vqg1ZNu4kPgnkX7ks5qcUA6gaJpZM4JYr5B
.

[HipsterBrown]

@reconbot How do you see if being used in your programs? Is it something called by a physical button (but not the on-board one) or from some kind of web UI?

reboot seems like a nuclear option since it tears down the entire program and that should be very clearly communicated to the Tessel developers.

[reconbot]

If I'm a developer prototyping an app I don't see a major use case.

If I'm a user of a tessel based app and the tessel is plugged in somewhere and hidden away and it starts to act funky then I see the value in this functionality. And if I'm a developer thinking of my user, then I see the value in the function call.

I kind of think we should be able to provide programmatically all the functionality of the tessel. We've hidden the openwrt backend from normal use and I think we should keep it hidden and continue to provide a nice clean api.

[dtex]

Some percentage of users have limited exposure to *nix (i.e. Windows and some Mac users) and as soon as you tell them to "just shell out to reboot" you've disrupted the amazing, simple developer experience that the Tessel 2 offers.

Assuming the use case is valid, it should be in the API.

[rwaldron]

I'll spend some time investigating this