Thank you for your bug report.
I think latter way is surely the better and more debianish way. Also numbering
should be the way to go.
I think it will take us a while to implement this, but we will very likely do
that.
Detecting multiple vhosts and offering user to split in multiple files would be
good, but not a cure for every desease, as some linux application stuffs
configuration outside <virtualhost> tags. At some point, manual intervention
would be necessary anyway.
Marking this as wishlist.
** Changed in: rapache
Importance: Undecided => Wishlist
Status: New => Confirmed
--
Support virtual host order
https://bugs.launchpad.net/bugs/241021
You received this bug notification because you are a member of Rapache
Developers, which is subscribed to Remote Apache Management tool .
Status in rapache: Confirmed
Bug description:
Supporting many virtual hosts on the same server often requires use of
wildcards. In this case, the order of virtual hosts matters. For example, a web
application which serves multiple domains simultaneously might be configured
with a ServerName of * and if other domains are also to be served by the same
Apache server they must be loaded prior to this one.
This requirement may be even more necessary on a development machine where many
different sites must be active which wouldn't exist on a single production
server.
One solution to forcing order is to place all virtual hosts in a single .conf
file. Another is to prepend an order code to the vhost conf files (e.g.,
1-siteone, 2-sitetwo) so they are parsed in the required order.
Rapache obviously does not (yet) support the former. I see only a single vhost
in Rapache for my single .conf file with many vhosts defined. Perhaps the
latter method can be used if order is specified.
_______________________________________________
Mailing list: https://launchpad.net/~rapache-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/people/+me/+editemails
More help : https://help.launchpad.net/ListHelp
