On Fri, 2017-09-29 at 11:25 -0700, Sean A wrote: > Sorry to dig up an old topic, but I just got nailed on this...as I > had forgotten about it. > > Has there been any update to being able to use foreman-installer with > preserving unrelated apache config files in /etc/httpd/conf.d? I am > trying to use an IP vhost to serve repositories and some other static > pages related to Foreman. I have the vhost in a separate config > file, but re-running foreman-installer blows it away. > > I know I could stuff those files down in /var/lib/foreman/public (or > whatever it is), but directory indexes are disabled, and I can't seem > to enable them and make that stick either.
No, our installer assumes Foreman gets the sole use of the box. If you're running Puppet for the rest of your config management, then one option is to add the foreman-installer modules to the rest of your Puppet manifest, and configure them to match the installer. This means all the vhosts will be in Puppet and the code that deletes unmanaged files won't touch them. Greg -- 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.
