Hi. I've recently merged the code for a new entity that runs a Node.JS application from a GitHub repository or a .tgz archive, closing the BROOKLYN-12 issue. It's only the first version, and there are some obvious features that could be added, like sensors to determine the state of the Node runtime, or better ways to customise the application and its dependencies. I'd also love some feedback on how it behaves with real-world code, as I've only tested it with a few toy example applications.
One really cool thing about this is that you can build a complex multi-service application that uses Node.JS using only the YAML blueprint. I wrote a short tutorial blog post about this, showing a Todo List application backed by a Redis store, here: - http://abstractvisitorpattern.co.uk/2014/08/brooklyn-and-nodejs-applications.html Another nice point that I didn't mention in the blog is that of course this works transparently with Clocker - the Node.JS service and the Redis store start in separate containers and talk to each other. So, please let me know if you have any suggestions or feedback. Since I'm mostly a Java developer, I'm probably missing out on some idiomatic patterns that are used when building Node.JS applications. If anyone can help make this more usable for the Node community, that would be great... Thanks, Andrew. -- -- andrew kennedy ? cloud engineer : http://blog.abstractvisitorpattern.co.uk/ ;
