On 06/04/17 22:39, Iain Hallam wrote:
> I've identified that SELinux was preventing Foreman from starting when
> using the passenger upstream repo, and replacing mod_passenger with the
> EPEL version fixed that.
>
> I'm currently applying a Puppet manifest using the puppet-foreman
> module, that simply says:
>
> class { '::foreman':
> admin_<settings> => ...
> }
>
> Is there any way in this type of installation to also set the Apache
> manage_repo to false so that the passenger repo never gets added?
Set it via Hiera, or possibly use:
class { '::apache::mod::passenger':
manage_repo => false,
}
--
Dominic Cleal
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
