Does node.js not include packages in opkg yet?
-
@Chris-Ward I compiled node from a completely different process than Onion's buildroot. It is also available at:
borromeotlhs/docker-onion-omega-nodejsThis image will contain the precompiled node and v8 binaries in them, I think in a folder called 'node_deploy'. That image will, I assume, have a working toolchain in it, though not entirely sure it was specifically suited to the onions hardware (tho node and v8 seem to work).
good luck!
-
@Theodore-Borromeo Great job Theodore!
-
-
@Theodore-Borromeo When I pull, I get a latest not found. Did you push this?
-
@Chris-Ward Uggh. I didn't push it, you're right. Please copy the Dockerfile at: https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/~/dockerfile/
into:
mydockerfileand then run:
cd mydockerfile/
docker build -t '<yourusername>/docker-onion-omega-nodejs' .until I get this uploaded after I build on my ancient personal machine
-
@Chris-Ward Turns out that I can't push a tag to an Automated Build, and as the build failed, I had to delete and recreate this repo.
Pushing now. . . Failed
Please try building as per above, and let me know. I'll have to rerun the build at home and push from there
-
@Theodore-Borromeo looks like the actual dockerfile (recipe) is gone now from docker hub. Do you want to email it to me? veggie2u at cyberward.net
-
@Chris-Ward ugh. I'm an idiot
Here is the github repo the automated build was supposed to work from:
https://github.com/borromeotlhs/docker-onion-omega-nodejs/blob/master/DockerfileHTH,
TJ
-
@Chris-Ward @Boken-Lin @Lazar-Demin The 'v1' tag was pushed successfully last night. This is what I used to create node and libv8 binary, and they will be in the 'node_deploy' directory of this image once pulled. Keep in mind, the image is 3GB: https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/tags/
-
Hey @Theodore-Borromeo it worked/downloaded with the command
docker pull borromeotlhs/docker-onion-omega-nodejs:v1Sweet.
Weird that docker said that it was a legacy repository.
I can't manage to get into the container. I am trying this command from the docker file:
docker run -d --net=none --expose=[9000] -p 127.0.0.1:9004:9000 -t alljoyn-builder:production(file says sudo, but not sure if you would need to)
For some reason I keep getting a "no matches found: --expose=[9000]" which is weird. I am wondering if it is something with my docker setup - I am using zsh not bash. I just got started with docker, and the examples all worked, but I can't launch this one.
-
@Chris-Ward you can run the image you pulled with:
docker run -it borromeotlhs/docker-onion-omega-nodejs:v1 /bin/bashyou pulled one image, and tried to run an older image via a tag that you may not have. I also tend not to bother with a daemon for build toolchains, but that's just me
-
Yes @Theodore-Borromeo I got it running. I was just trying to follow the suggestion from the docker file. I don't get what they were trying to get at. I managed to get to a bash prompt with pretty much the same command as above. I looked around, saw how you compiled, but haven't had a chance to do anything else yet.
-
@Chris-Ward yeah, apologies that the comments from within the Dockerfile were from a previous project, and thus had 'hints' for myself when I first started using docker. Coincidentally, alljoyn for the wndr3700
alljoyn, if it were useful or more widely adopted might be a great lib for the omega if it had bt. . .
-
So what is the status of this? Will we always need a usb stick connected to our onion in order to use Node.js?
-
@Stephen-Tunney With node version 0.10.5, it only takes up around 3 MB of space. So you should be able to run it entirely on the Omega's flash.
-
@Dan-L. are you still working on porting Samsung's IOT.js?
-
@Fred-Blais Yup.
-
anything to report?
-
is it even possible to get npm running?
related, It might be worth contacting the NodeJS foundation to see if Onion can help them add better MIPS support. If Onion were able to donate a few Omegas, it'd surely go a long way.
-
@Fred-Blais Not yet, unfortunately... But we won't stop until it's done! Getting Javascript support is something we've promised, and we'll deliver it in both Node.js and IoT.js
@Christopher-Hiller Yes,
npmis very doable. The only hard part is thenode-gypstuff which compiles non-Javascript source to binary (because Omega doesn't have a huge amount of computing power), but our solution to that is to build anpmrepo with pre-compiled modules that can be just installed withnpm.
