Closed (won't fix)
Project:
Barracuda
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Sep 2011 at 00:36 UTC
Updated:
2 Oct 2011 at 18:06 UTC
Jump to comment: Most recent
Would be nice to see an option to install a node.js instance on BOA.
Some good modules (like activity) providing integration for node.js.
Main project page
Here is the drupal module
http://drupal.org/project/nodejs
Found a good article for an upstart script for node.js as daemon.
http://kevin.vanzonneveld.net/techblog/article/run_nodejs_as_a_service_o...
Comments
Comment #1
bennos commentedOops one URL missing.
Main Project URL
http://nodejs.org/
Comment #2
danielm commentedSubscribing
Comment #3
omega8cc commentedThis is beyond the scope of the BOA project.
You can always play with Node.js on the same server if you wish, but there are no plans to add this as a feature.
Comment #4
danielm commentedSorry, maybe you change your mind in the future.
Comment #5
omega8cc commentedI will add a short reasoning for our "no" to Node.js as a BOA feature.
The BOA plan is not about creating any never ending bundle-stack like Virtualmin. It is about complete, but as minimal as possible LEMP stack allowing you to run Drupal at max possible speed. Nothing less and nothing more. While Node.js is a very cool and crazy fast technology, it has nothing to do with running Drupal at max speed. It is a different technology for different things.
Drupal itself will not be more cool or faster thanks to attempts to use Node.js integration in some areas. If you want a fast CMS leveraging the Node.js speed, try http://calip.so. But it is unrelated to the BOA project completely. We don't plan to "marry" PHP/Drupal oriented stack with Node.js stack. If we will ever use Node.js for anything, it will be a separate project.
That is why we are leaving this for the admin decision and deny this feature request - there is no sense in adding and supporting completely different stack as a feature if we (BOA devs and Omega8.cc) will not use it for anything - at least in the Drupal context.
Of course anyone can fork the project on GitHub or here at d.o and extend it to support also Node.js - and then provide Node.js related support for the community.
Comment #6
druvision commentedI understand what you write but the post is 2-years old.
At least, provide connectivity with an external node.js server like heroku.com
Comment #7
omega8cc commentedWhat you mean by "provide connectivity" ?