NPM Install Issues about calipso HOT 17 CLOSED

This is definitely a known issue, I will raise bugs on both bcrypt and node-expat libraries that try to get those modules to install their dependencies, otherwise we need to get the install script to install these.

Did you use the /bin/install.sh?

from calipso.

Yep, to no avail using the latest pull. It seems that everything else works fine, it's just expat and bcrypt that cause problems (for me anyway). I'm pretty sure I had the same problems last time around (maybe a week ago?). Just for clarity, I'm using the latest stable version of both Node and NPM.

from calipso.

No problem, both of those have dependencies on installs outside of npm's control at the moment, so I need to get those checks and installs written into the install.sh script or just make it very clear that you have to install both those libraries first ... glad you persevered and got it working!

from calipso.

Of course! I was actually getting my environment set up to start contributing this weekend. It's little late EST time today, but on my agenda for tomorrow is sorting through the code and looking at the standards docs at the very least! I'm very much interested in the progression of this project.

from calipso.

@dsimmons

If you saved it anywhere, can you paste what the output of install.sh was? I'm wondering why it didn't fail. If not, I'll see if I have time to set up a default ubuntu-vm and see what's happening on install.sh

from calipso.

I unfortunately did not, and obviously it doesn't do anything now I've manually fixed the dependencies. I'm looking through the install script and it looks like the check is in there, maybe I missed it in all of the output?

from calipso.

@dsimmons, I'm not sure, actually - the script should have failed. I suppose its possible you just thought the script was finished and you just moved on. Nonetheless I'll try to test this on a VM sometime this week.

from calipso.

It definitely might have failed, but there was a bunch of NPM error output (mainly regarding expat), so there's a very good chance that I missed it favor of the verbose, colored NPM text. Also in regard to install.sh, my NODE_PATH wasn't set correctly initially. I've since manually fixed it, but it seems like for the sake of the Makefile, it assumes that Expresso is installed with NPM globally? I don't know if this is the default, but 'npm install' had installed it locally (to ./node_modules) and wasn't able to find it for the sanity tests until I did 'npm install -g expresso'.

from calipso.

yeh I'm having problems getting calipso to communicate with mongodb, was wondering if you could share how to set NODE_PATH, I think this is where the problem lies

from calipso.

I don't set node_path, the default install instructions put it in the right place with the right settings for me (Ubuntu 10/11). What is the error?

from calipso.

I'm on mac osx, when I run node app in the calipso folder I get "error connecting to mongodb, maybe it's not running?" I will try to reinstall it again

from calipso.

I don't have a mac to test anything on, so very difficult at this stage to say what you need to do to get it to work ... maybe an excuse to buy myself a new laptop?! :)

from calipso.

Sorry, I've been primarily out of town for the past few weeks and haven't caught up on emails. As for setting your NODE_PATH, I have the following in my ~/.bashrc:

export NODE_PATH="/usr/local/lib/node_modules"

Of course, adjust the above for the location of your node_modules directory. I believe mine is the default from the install script. Also note that I chowned my /usr/local/ directory recursively to my user account so that I didn't have to use sudo to update NPM.

Sorry for the delayed response, let me know if you have any issues!

from calipso.

Also for reference, as to maybe help someone out in the future: I wiped and re-installed Node, NPM, MongoDB, and Calipso. I ran into 2 different problems this time.

1. Rather than manually compiling Node from source like I had been previously doing, this time around I used Chris Lea's PPA (it looks like he keeps it up-to-date with the latest stable version, my main concern if using a package manager). However, it doesn't include node-waf for whatever reason. Because a few of the NPM dependencies require node-waf, I ended up building Node in a temp directory and symlinking node-waf to /usr/bin. Seems to work fine, but in the future I might just copy the binary and see if that works.

2. I had to manually perform a make on node_modules/mongodb. It seems like there's something funky going on with its install script. I posted an issue about it here: https://github.com/christkv/node-mongodb-native/issues/286.

I realize that neither of these are the fault of Calipso, but caused problems nonetheless. In the event that anyone else runs into either of these problems, seems to be working fine with the above two fixes!

from calipso.

Thanks - very useful info.

I'm in the middle of re-factoring the module management to allow for modules to import their own dependencies, hence the core won't rely on mongodb or expat (hence resolving many of the initial install issues). Of course it means that the issues will still occur, but isolated around those that want to use specific features ...

Watch this space, hope to have it up in the next 2-3 days.

from calipso.

That will certainly be a welcomed addition! Looking forward to the changes!

from calipso.

Ok, this is now almost all done in its first phase:

Default user installation should be via npm, not github (only grab code from here if you want to hack the core).

npm install calipso -g

calipso then becomes a command:

calipso modules list
calipso modules install feeds (at the moment this reinstalls its dependencies only, but later will download and install it if it doesn't exist already)
calipso modules check (checks all)
calipso modules enable feeds (enable / disable from cmd line)
calipso modules disable feeds (enable / disable from cmd line)

calipso server (runs server - same as node app)

The core now has less dependencies (only those really required for core at the moment).

Also, the module loading will fail gracefully if a modules dependencies aren't met. Hopefully will be a better experience installing and set us up for a module repo that enables quick installation / mgmt of additional modules ...

Clifton

from calipso.