hi folks i am using the latest apache2 cookbook from opscode to
configure my apache server I have already added my own virtual hosts
recipes, for some reason I cannot seem to be able to disable the default
and default-ssl sites , I red the README and tried apache_site “default”
“disable” , apache_site “default” “false” but nothing seems to trigger
the a2dissite code.
hi folks i am using the latest apache2 cookbook from opscode to configure my
apache server I have already added my own virtual hosts recipes, for some
reason I cannot seem to be able to disable the default and default-ssl sites
, I red the README and tried apache_site "default" "disable" , apache_site
"default" "false" but nothing seems to trigger the a2dissite code.
hi folks i am using the latest apache2 cookbook from opscode to configure my
apache server I have already added my own virtual hosts recipes, for some
reason I cannot seem to be able to disable the default and default-ssl sites
, I red the README and tried apache_site "default" "disable" , apache_site
"default" "false" but nothing seems to trigger the a2dissite code.
I wanted to minimize the amount of apache reconfiguration done on each
chef run, and since a reconfig triggers an apache reload, I wanted to
prevent that as much as possible as well.
As well as make it configurable outside the cookbook itself, to
maintain a "pristine" installed cookbook.
Curious - does this mean that on a chef run, you're enabling the
default in apache2::default and the disabling in your custom recipe?
hi folks i am using the latest apache2 cookbook from opscode to configure
my
apache server I have already added my own virtual hosts recipes, for some
reason I cannot seem to be able to disable the default and default-ssl
sites
, I red the README and tried apache_site "default" "disable" ,
apache_site
"default" "false" but nothing seems to trigger the a2dissite code.
Yes you are right I am running the chef::default and then my custom
recipe disabling the default site , by all means its not an elegant
workaround but it works , I will have to wait for the new attribute
on 1.1.10 ... this will enable me to remove my code snippet.
Kobi.
On 06/24/2012 03:25 PM, Mike wrote:
Glad to hear you got it.
I wanted to minimize the amount of apache reconfiguration done on each
chef run, and since a reconfig triggers an apache reload, I wanted to
prevent that as much as possible as well.
As well as make it configurable outside the cookbook itself, to
maintain a "pristine" installed cookbook.
Curious - does this mean that on a chef run, you're enabling the
default in apache2::default and the disabling in your custom recipe?
hi folks i am using the latest apache2 cookbook from opscode to configure
my
apache server I have already added my own virtual hosts recipes, for some
reason I cannot seem to be able to disable the default and default-ssl
sites
, I red the README and tried apache_site "default" "disable" ,
apache_site
"default" "false" but nothing seems to trigger the a2dissite code.