Vincent Veyron wrote:
..
tested it. See :
http://extranet.france-prevoyance.fr/clients/login
and :
http://as-pro.biz/clients/login
An additional comment :
The logic you have now (with the login module checking the hostname and choosing the logo
in function of that), is fine as long as the logo is the only thing which varies.
But customers are fickle, and they change their mind easily.
It would not be surprising if once you give them a different logo, some of them come back
to you, wanting their own special "look" in all the pages of their site.
And if you try to adopt the same logic for such changes, you are going to end up with
horribly complicated perl modules.
That is why I was suggesting multiple <VirtualHost> sections.
Instead of having a VirtualHost like
<VirtualHost */*>
ServerName "as-pro.biz"
ServerAlias "customer1.biz"
ServerAlias "customer2.biz"
etc..
..
</VirtualHost>
you may want to try
<VirtualHost */*>
ServerName "as-pro.biz"
..
</VirtualHost>
<VirtualHost */*>
ServerName "customer1.biz"
..
</VirtualHost>
<VirtualHost */*>
ServerName "customer2.biz"
..
</VirtualHost>
<VirtualHost */*>
ServerName "customer3.biz"
..
</VirtualHost>
This way, you can give each customer its own "special things" whenever they want, without
interfering with your perl modules (or the other customer sites).
Your $r->hostname will still work like before, and there will still be only one Apache
server. It will just change its configuration at each request, to match the request Host:
header with the appropriate VirtualHost that has that ServerName.
But then, you can give each one its own "/images" alias, pointing to a directory with its
own logo, and its own "/css" alias, pointing to its own stylesheets etc..
That is much more flexible (and a lot less work in the long term) than adapting your
software each time a customer wants something different.
