-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decouple management of Apache virtual host #31
Comments
+1 https://forge.puppetlabs.com/puppetlabs/apache seems to be widely used and accepted. I'm not sure how much benefit there is for the author to re-invent the wheel on apache/httpd management. |
@neoice : Both this nagios module and my apache_httpd module pre-date the puppetlabs-apache module being in an acceptable state ;-) |
So should I submit the above as a pull request? |
Ping - last issue that's standing in the way of me using this module rather than a local fork |
@alexharv074 do you have a PR? I'd love to take a look and maybe use it myself. |
@neoice I'm afraid I gave up trying to get the author's attention but my diff is above. |
@thias ping ping ping. :) |
Finally I have two patches that attempt to decouple management of the Apache virtual host so that the Puppet Labs apache module can be used if desired to manage the virtual host instead. I apologise that I haven't fully understood the problem the author was trying to solve or all aspects of his solution although I think the concept is valid. Would a cleaned up version of the patches below be welcome?
And
The text was updated successfully, but these errors were encountered: