[chef] Re: Application cookbook

[Haselwanter Edmund < >]

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.

Is there no way of separating out the commonalities between them other than having them all in the same cookbook?

recently I did some rework on that. have a look at:

http://www.iteh.at/en/blog/2011/06/23/deployment-of-java-web-applications-with-chef-from-opscode/

https://github.com/iteh/vagrant-demos/tree/master/vagrant-java-application-reworked

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] = app

application_java_webapp "jolokia-java_webapp" do

  context_cookbook "zabbix"

end

application_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

--

DI Edmund Haselwanter, "> , http://edmund.haselwanter.com/

http://www.iteh.at | http://facebook.com/iTeh.solutions | http://at.linkedin.com/in/haselwanteredmund