[chef] Re: Re: Re: Re: Re: Is this a bug in the apache2 cookbook?

[AJ Christensen < >]

On 10 January 2012 10:16, Tim Uckun 
<
 >
 wrote:
> On Tue, Jan 10, 2012 at 10:13 AM, AJ Christensen 
> <
 >
>  wrote:
>> Right, the 'a2enmod' / 'a2dismod' script manages the symlinks. On
>> non-ubuntu/debian systems, this has to be managed by robot.
>
> Again the issue is not the management of the files the issue is the
> creation of the files. The apache2 recipe does not create the .load
> file for ubuntu/debian based systems (at least not for the passenger
> module).
>
> Maybe the fault is with the passenger_apache2 recipe I don't know but
> in order to install passenger on ubuntu I had to add ubuntu to the
> list like this...

Yes, the fault is with the passenger_apache2 recipe.

Brutalizing the apache2 module definition (used by all of the
apache2::mod_* recipes) will mean that your system is generating .load
files where it is not necessary to do so -- the .load files are
provided by the system with the libapache2-foo-bar packages.

I'd suggest rendering the passenger .load module configuration file to
the "mods-available" directory for Apache2 then using the standard
a2enmod/a2dismod / apache2_mod definition code, without modification.

Cheers,

AJ

>
> if platform?("redhat", "centos", "scientific", "fedora", "arch",
> "suse" , "debian", "ubuntu")
>    file "#{node['apache']['dir']}/mods-available/#{params[:name]}.load" do
>      content "LoadModule #{params[:name]}_module #{params[:module_path]}\n"
>      mode 0644
>    end
>  end