enable overriding mod-level parameters for apache::mod::passenger

apache::mod::passenger didn't accept/pass (optional) mod parameters
through to apache::mod, so only auto-generated module parameters were
used.  Without this option apache::mod::passenger could not be used in
conjunction with passenger modules beyond those generated by OS package
system (in particular, modules compiled via
passenger-install-apache2-module, which use differing paths).  This
commit enables passing in all parameters used with "apache::mod",
documented in the passenger README

includes basic spec/acceptance tests; verifying a default installation
as well as passing in module loading parameters.

new tests revealed undocumented Redhat dependencies on a passenger-
specific repository as well as the EPEL repository; as a first step
these dependencies are being manually resolved during setup for the
acceptance testing suite.
Add extra parameters to mod::php
Merge pull request #681 from CIRB/master

fix missing ensure on concat::fragment resources
fix missing comma in sample config

there was a missing comma in the sample to handle redirect from
http to https site, making it invalid puppet syntax.
Merge pull request #683 from sdague/master

fix missing comma in sample config
Allow extending LogFormats

by passing a hash of additional LogFormats, we can extend the existing
definitions.
Fixed travis by updating Gemfile to pin Rake to 10.1.1

The latest Rake update requires Ruby >= 1.9. This update
fixes the failing 1.8.7 tests by pinning Rake to the last
supported version on ruby 1.8.7.
rename package param, add tests and documentation
Merge pull request #685 from blkperl/fix_rake_18

Fixed travis by updating Gemfile to pin Rake to 10.1.1
Merge pull request #684 from oxilion/php-parameters

Add extra parameters to mod::php
Fix typo in service.pp doc
Merge pull request #686 from ckaenzig/typo-in-service

Fix typo in service.pp doc
Merge pull request #682 from igalic/logformat

A first stab at extending LogFormats
Enable overriding mod-level parameters for apache::mod::passenger

Apache::mod::passenger didn't accept/pass (optional) mod parameters
through to apache::mod, so only auto-generated module parameters were
used. Without this option, apache::mod::passenger could not be used in
conjunction with passenger modules beyond those generated by the OS
package system (in particular, modules compiled via
passenger-install-apache2-module, which uses differing paths). This
commit enables passing in all parameters used with "apache::mod",
documented in the passenger README file.

Modified default RedHat passenger parameters for cleaned-up
installation (prior parameters worked with Apache, but broke
passenger-* utilities, incl. passenger-status & passenger-root).

Updated spec/class tests to verify mod-level parameters; also,
updated RedHat tests to accomodate updated default parameters.

Added spec/acceptance tests for passenger, verifying default
installations for RedHat and Debian systems. RedHat installation test
installs (required) EPEL and http://passenger.stealthymonkeys.com
package repositories.
Merge branch 'mod-passenger-2' of https://github.com/jonoterc/puppetlabs-apache into mod-passenger-2

Conflicts:
	manifests/mod/passenger.pp
	manifests/params.pp
fix inverted ssl compression

Apache 2.4 defaults SSLCompression Off. The ssl module provides a
parameter for ssl_compression which defaults false. If it is set
to true, the template actually would add another SSLCompression Off
stanza (not the expected SSLCompression On).
allow global setting of SSL cipher

ssl_cipher is setable per vhost already, this makes it an option
that can be sent once per the entire configuration instead of at
each vhost.
Merge pull request #687 from jonoterc/mod-passenger-2

Enable overriding mod-level parameters for apache::mod::passenger
Merge pull request #688 from sdague/master

ssl tweaks
Allow Apache service not to be managed by Puppet

Currently Apache can either configured to be 'running' or 'stopped'. In our cluster setup Apache is managed by Pacemaker, so Puppet should not interfere. Setting ensure to 'UNSET' will now set ensure to undef for the Apache service.