- From: <
>
- To:
- Subject: [chef] Can someone validate my understanding of chef?
- Date: Wed, 6 Oct 2010 00:55:47 -0700 (PDT)
Hello fellow cooks,
I am looking for the best way to structure the following.
We have several legacy java websites running apache, tomcat & mysql.
Currently I am thinking about each site would have it's own cookbook and
branch
in the node, such as
the one below:
"example.com": {
"name":"example.com",
"admin":"
",
"url":"example.com",
"aliases":["www.example.com","example.co.uk","www.example.co.uk"],
"tomcat_port":"41511",
"jdbc_url":"jjdbc:mysql://host:3306",
"jdbc_user":"db",
"jdbc_password":"password",
},
The cookbook would define requirements such as apache, mysql and version of
java, but would
defer any configuration to a set of common definitions.
The website cookbook being a container to get configuration to the various
definitions. This would hopefully
also mean that production, staging and development Nodes would be a copy and
paste with a few tweaks.
Does this sounds like the chef way to go?
Cheers
Jono
- [chef] Can someone validate my understanding of chef?, jono, 10/06/2010
Archive powered by MHonArc 2.6.16.