Hi,On 29.06.2011, at 15:46, Tim Diggins wrote:Ohai chefs!
Can anyone answer why the application cookbook is grouped together? It seems like it would make more sense to have a rails cookbook, a java-container (or tomcat) cookbook, a django cookbook.I think that depends were you want to do the "data driven" part. at the moment the application coobook loops through all databag application definitions and runs the recipes for that.recently I did some rework on that. have a look at:Is there no way of separating out the commonalities between them other than having them all in the same cookbook?were I moved the recipes to definitions.then you can do something like:app = JSON.parse(File.open(File.join(File.dirname(__FILE__),"../databags/jolokia.json")).read)node.run_state[:current_app] = appapplication_java_webapp "jolokia-java_webapp" docontext_cookbook "zabbix"endapplication_tomcat "jolokia-tomcat"node.run_state.delete(:current_app)in ay other recipe------But this is still a very good question. Were to put all the supporting stuff?If I have a reverse proxy for tomcat, should it go in the application cookbook, the apache cookbook, or the tomcat cookbook ... ?cu edi
Archive powered by MHonArc 2.6.16.