Project

General

Profile

« Previous | Next » 

Revision e998d702

Added by Igor Galić over 8 years ago

allow the configuration of serveraliases

In some environments, foreman might have a different name to different
networks. Different implementations of SSL (jruby, curl-tls, openssl),
appear to have different levels of tolerance for such a certificate
(mis)configuration in Apache httpd's vhost.

Closes GH-401

View differences:

manifests/params.pp
$foreman_password = undef
# Should foreman act as an external node classifier (manage puppet class
# assignments)
$enc = true
$enc = true
# Should foreman receive reports from puppet
$reports = true
$reports = true
# Should foreman receive facts from puppet
$receive_facts = true
$receive_facts = true
# should foreman manage host provisioning as well
$unattended = true
$unattended = true
# Enable users authentication (default user:admin pw:changeme)
$authentication = true
# configure foreman via apache and passenger
$passenger = true
$passenger = true
# Enclose apache configuration in <VirtualHost>...</VirtualHost>
$use_vhost = true
$use_vhost = true
# Server name of the VirtualHost
$servername = $::fqdn
$servername = $::fqdn
# Server aliases of the VirtualHost
$serveraliases = [ 'foreman' ]
# force SSL (note: requires passenger)
$ssl = true
$ssl = true
#define which interface passenger should listen on, undef means all interfaces
$passenger_interface = undef
# Choose whether you want to enable locations and organizations.

Also available in: Unified diff