digitalbutter / cookbook-node Goto Github PK

I'm a little new to chef, but I think this is an error. Because the action :start, :stop, and :restart parts of the provider just call exec, they can fail if the service is already running.

My application recipe includes a node_service section and I'm pretty sure I want it to be action :start, but that doesn't work because the exec fails if the process is already running.

I have a series of changes that make it use the upstart service properly so that subsequent runs of chef-client don't error out.

Am I correct in my thinking?

A version bump on the Opscode site would be great so that f2641f7 is automatically pulled in.

Thanks

While using Chef, Berkshelf, AWS, etc, I got an error while installing the node cookbook because 'make' was not found. This is part of the build-essential community cookbook.

Best AFAIK practice is to:

• Include the dependency in the metadata.rb/json
• Include the "build-essential::default" in a recipe

Let me know if there's something I'm missing, or if there are any questions! I'll try to look into this myself when time permits :).

Hey guys, took me a little while to find this github profile because i was looking for the homepage meta data at the top of the opscode community site. I don't know how to update that but it would be worth adding the link that is in your readme to that metadata.

Example: https://cloudup.com/c7yt3yJJuyQ

Ubuntu comes with a nodejs package. Rather than waiting for nodejs to compile on all my servers, it might be nice to use the package instead.

I would be willing to write a patch, if you are open to accept it.

Hi @edbo ,

nodejs v2.0.0 from redguide is out and released.
You can now tag your cookbook as deprecated on supermarket to nodejs.

\o/