Currently i have them setup like the following:
project
application
public
admin
index.php
www
index.php
blog
index.php
each index.php has its own bootstrapper which defines its own
application bootstrap class, and possibly use multiple configs, very
similar to ZFPlanet demo.
On 2/19/2010 3:10 PM, Mark Wright wrote:
They look like 3 distinctly different sites so why not use different
public roots? I am currently working on a site with a .com and .com.au
domain where aside from some locale and some translation between us/uk
english (like color vs colour) the sites are the same so I use the
same document root. I have 2 virtual hosts which set an environment
variable indicating the country.
Mark
On Fri, Feb 19, 2010 at 11:54 AM, Paul<[email protected]> wrote:
Similar to the question asked earlier to subdomains... does it always make
sense to have all entries into an application be from within the public
folder?
An example of this would be a site with 3 subdomains - www.mydomain.com,
admin.mydomain.com, and blog.mydomain.com.
I think it make sense for some of these, in particular, the admin, to have
its own application bootstrap. Something similar to Patraic Brady's
ZFPlanet, where the cli interface had its own bootstrap.
Would it make sense to alter the apache .htaccess file to look at the host..
or have 3 different document roots.
Trying to prevent duplication, yet give each entry it's own meaning /
context.
Also what would you call these, sites, portals, applications, etc?
Thanks,
Paul
