I have a Zend_Application that I would like to deploy for several different customers on one host. Review of documentation and discussions reveals that this is easy enough with: 1. A virtual host pointing to an application instance specific to a customer 2. A virtual host pointing to a "site" folder with customer specific configuration; allowing a single instance (copy) of the application on the server. You might load config based on server name or domain name as defined by the virtual host that gets hit. See: http://zend-framework-community.634137.n4.nabble.com/Multiple-sites-with-same-code-td660524.html
Irrespective of the two approaches mentioned above I'd end up presenting each customer something along the lines of: http://acme.hotzfapp.com http://dinoco.hotzfapp.com http://sienar.hotzfapp.com What I'm trying to figure out is how to present urls like the following whilst maintaining the cleanliness of direct "public" asset inclusion: http://www.hotzfapp.com/acme http://www.hotzfapp.com/dinoco http://www.hotzfapp.com/sienar In other words, with the scheme I'm suggesting I still want to be able to link to assets via link href="/media/css/basic.css" and not link href="/acme/public/media/css/basic.css" Anyone implemented anything similar to this? Thank you for any suggestions, direction, or pointers. -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/vary-Zend-Application-configuration-based-on-requested-url-tp3066770p3066770.html Sent from the Zend Framework mailing list archive at Nabble.com.
