t2 restart <file> --type=flash|ram, defaults to "ram". Fixes gh-264

[rwaldron]

No description provided.

[johnnyman727]

I might add 'Restart a previously deploy script in RAM...'

[rwaldron]

Fixed in next commit

[johnnyman727]

@rwaldron It seems like you shouldn't be specifying an entry point. To me, it's most intuitive to just run

t2 restart

or

t2 restart --push

When would you want to restart a script that wasn't the one that you just deployed?

[rwaldron]

@johnnyman727

rwaldron at new-host-2 in ~/robotz/tessel-gps-monitor
$ t2 restart  index.js
INFO Connecting to Tessel...
INFO Connected to bishop over LAN
WARN "index.js" not found on bishop

[rwaldron]

When would you want to restart a script that wasn't the one that you just deployed?

There is no memory from one cli call to the next, so the name of the file that the user wants to restart is not concretely knowable. There could be several files in the root of a project directory that get deployed on either a run or push— it's impossible to know which one the user wants to restart, I can imagine deploying different versions in one t2 run ... and then restarting from one or the other. It would be super messy to look at all files in the remote directory and try to figure out which is the one to restart. What we can do, is allow t2 restart and let it read the local package.json for a main entry; if the user needs to be explicit, they can be. This will cover the both of the most common cases.

[johnnyman727]

Love it! Tried it out and it works great. Feel free to merge!