You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am new to the BeagleBone community and I would like to know if it is possible to deploy JavaScript code remotely to the BeagleBone?
Until now I always coded on the BeagleBone (using the Cloud9 environment) itself. But I would like to code on my personal computer and then deploy it from there to the BeagleBone. Is this possible?
I know that the Tessel microcontroller supports this way of coding by running tessel run my-app.js.
i do my dev on my laptop and push to github, then pull from the BBblack.
You could also do a rsync or an scp from your dev host to your BBblack. If you install something like pm2 and use it to watch wherever you're putting your project, it will restart the app if it detects changes, so that after each update iteration, it automatically runs the app.
another possibility (but is kind of overkill) is to run a git server on the BBblack and just push your code there.
Makes sense to add a over the internet option? Using something like gists from GitHub? Not sure how we'd get the output back? Maybe using another gist? (not sure if this makes sense for us, but would love to have Particle.io like functionality)
BTW, this really needs some security. That should trump some of this other development. Just some kind of secure session creation when using the web server.
From @bennyn on March 5, 2017 18:45
Hello, I am new to the BeagleBone community and I would like to know if it is possible to deploy JavaScript code remotely to the BeagleBone?
Until now I always coded on the BeagleBone (using the Cloud9 environment) itself. But I would like to code on my personal computer and then deploy it from there to the BeagleBone. Is this possible?
I know that the Tessel microcontroller supports this way of coding by running
tessel run my-app.js
.Copied from original issue: jadonk#148
The text was updated successfully, but these errors were encountered: