Skip to content
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

Closed
mw44118 opened this issue Feb 27, 2013 · 6 comments

Comments

@mw44118
Copy link

mw44118 commented Feb 27, 2013

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.

@dperetti
Copy link

dperetti commented Mar 8, 2013

Worse than that, pre-existing enabled sites are "purged" by apache::init.pp.

@mw44118
Copy link
Author

mw44118 commented Mar 8, 2013

Oh, yeah, that is kind of gnarly. Glad you called that out! That's a bigger bug than my little peeve.

@HNygard
Copy link

HNygard commented Apr 9, 2013

+1

@stolsvik
Copy link

stolsvik commented Apr 9, 2013

+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".

@jefflaporte
Copy link

+1

@bmurtagh
Copy link

+1

@hunner hunner closed this as completed in 8d7bdc5 Jul 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants