Hi, The way I did this was by using the domain name as the name of the config files which held the layout paths for all site specific media and stylesheets. The code base was common across all sites and controlled via a single backend administration module that exposed different functionality to the frontends.
Regards, -----Original Message----- From: Eugen_cro [mailto:[email protected]] Sent: 27 May 2009 08:49 PM To: [email protected] Subject: [fw-general] Multiple sites with same code I have one theoretical question: lets say I have a web application that would be used by 10-20-30 different sites (they will all be hosted on same server). It's still in early stage of development and I don't want to get too far ahead of my self :) Since the code will be practically the same (library and mvc) what would be the best option so I don't have to duplicate code over and over again (except storage, that will be pain in the ass to update later).. Sites would only be different in domain ofc, database and public directory. I was thinking to make some sort of configuration in each public/index.php and then pass those options to bootstrap (like domain, title, path to public, database info, etc..).. Now I'm not quite sure how good is this idea, so any suggestions are more then welcome. ----- Regards, Eugen -- View this message in context: http://www.nabble.com/Multiple-sites-with-same-code-tp23748572p23748572.html Sent from the Zend Framework mailing list archive at Nabble.com.
