schisamo
| Name: | Seth Chisamore |
| Member for: | over 2 years |
| Last login: | 4 months ago |
| Twitter: | http://www.twitter.com/schisamo |
| IRC: | schisamo |
| Location: | Atlanta, United States |
| activity | item | |
|---|---|---|
|
Apr 20
|
New Cookbook Version | |
|
Apr 20
|
New Cookbook | |
|
Feb 23
|
New Cookbook Version | |
|
Feb 19
|
New Cookbook Version | |
|
Feb 17
|
New Cookbook Version | |
|
Feb 17
|
New Cookbook | |
|
2011
|
New Cookbook Version | |
|
2011
|
New Cookbook | |
|
2011
|
New Answer |
virtual host creation
The apache2 cookbook comes with a definition called `web_app` for doing just this thing. Example usage might look something like this:
array_of_apps.each do | app |
web_app app do
template "web_app.conf.erb"
docroot "#{node['apps']['dir']}/#{app}"
server_name "#{app}.#{node['fqdn']}"
server_aliases "#{app}.#{node['fqdn']}"
notifies :restart, resources("service[apache2]")
end
end
This example assumes each app has a subdirectory at node['apps']['dir'] that will become the docroot for the vhost and you would like a subdomain created for each app. The actual array of apps/vhost names to iterate over should probably come from a data bag so adding new vhosts wouldn't require a code/cookbook update! Yeah data-driven infrastructure.
more →
|
|
2011
|
New Answer |
Contributing changes to cookbooks back to the community
The easiest way is to follow the steps laid out in our [How to Contribute Guide][1]. Basically you do the following:
1. Ensure you signed a CLA and are listed on the [Approved Contributors List][2]
2. Open JIRA ticket in the COOKBOOK project
3. Fork the github.com/opscode/cookbooks
4. Create a branch named after your ticket number (something like COOK-343)
5. Commit your enhancements/changes to this branch; push branch to github
6. Resolve your ticket with a link to your github branch
[1]: http://wiki.opscode.com/display/chef/How+to+Contribute
[2]: http://wiki.opscode.com/display/chef/Approved+Contributors
more →
|
