Node dependency check fails on linux about gae-init HOT 6 CLOSED

Which got things even worse, actually since its not appearing at /usr/env/bin/ I have removed everything and added nodejs from ppa:chris-lea/node.js and everything seems to be normal. I ll close it for now, but maybe there is something we should keep an eye on.

from gae-init.

Using Xubuntu 14.04 in a VM, I've seen similar issues starting clean... I recall that I had to ./run.py -C and ./run.py -s a few times in order to kick it into gear. Seemed like on first try it didn't get all the node or bower stuff. On the other hand, I might not have followed the fine manual to the letter...

from gae-init.

@mdxs It's tricky because sometimes some of the installations are not completing successfully so some of the files might be missing in the end before running the ./run.py -s and the -C basically tries again.

It's actually even harder to get it with the first run on different Windows versions and at one point we might want to write somewhere the common problems during the first run..

from gae-init.

Will try to make notes (and compare with docs/manual) on next clean setup...

from gae-init.

I noticed also in bower install it gets "stuck". What I usually do in order not to wait after run.py -C I Ctrl+C when bower install, I let it install the pip things and start the server. On a separate terminal I rm -r node_modules && npm install which resolves nicely. What I notices is if we pass a parameter registry in run.py, npm install --registry http://registry.npmjs.eu/ it usually works out of the box, so I am guessing are failed resolves from .org npm repositories.

from gae-init.

Another trick I pulled, in the past is to install node-legacy package (sudo apt-get install node-legacy), which fixed the issue since it referes to node as node and not as nodejs. I hope it helps somehow in your research.

from gae-init.