Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct node.js setup may be needed. #5

Open
sotirisb opened this issue Jul 19, 2013 · 2 comments
Open

Correct node.js setup may be needed. #5

sotirisb opened this issue Jul 19, 2013 · 2 comments

Comments

@sotirisb
Copy link

Hi, it seems the current version of setup.sh does not generate an up-to-date node.js version on a fresh EC2 Ubuntu micro instance. Unsure why, but upon completion 'node --version' will yield v0.6.12. This hinders loading jshint (which fails during to version mismatch) as well as additional node modules such as express. Perhaps the following sequence (taken from the course lecture) should be incorporated in setup.sh:

!/bin/sh

sudo apt-get update
sudo apt-get install -y python-software-properties python g++ make
sudo add-apt-repository -y ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install -y nodejs

@balajis
Copy link
Contributor

balajis commented Jul 19, 2013

Seems to work for me. Did you try logging out and logging back in? Some of the profile changes don't fully apply until then (yes, you can also source config files, but we'd ideally need to engineer them to be idempotent). Try booting up a new instance and running these commands:

wget https://raw.github.com/startup-class/setup/master/setup.sh
chmod u+x
./setup.sh

I then get

node --version
v0.10.12

@sotirisb
Copy link
Author

Thanks. I could not replicate the problem in a new instance. I probably took a wrong turn somewhere. Apologies for the false alarm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants