-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
debian virtual hosts should be created in sites-available with symlink in sites-enabled #161
Comments
Worse than that, pre-existing enabled sites are "purged" by apache::init.pp. |
Oh, yeah, that is kind of gnarly. Glad you called that out! That's a bigger bug than my little peeve. |
+1 |
+1, and +1. In my opinion, this is quite bad, both not following conventions, and completely ignoring any existing config by simply removing everything in there. That's not clean, not modular, not "separation of concerns", and not "mind your own business". |
+1 |
+1 |
The debian convention is to make a file in /etc/apache2/sites-available for each virtual host, and then use the a2ensite script to enable that virtual host.
The a2ensite script sets up a symbolic link pointing to the file from sites-enabled.
This puppet module instead just drops the file right in sites-enabled.
It works OK, but it isn't conventional.
The text was updated successfully, but these errors were encountered: