Thanks all, I think this is probably the option that I'm going to take. 2009/1/5 Pádraic Brady <padraic.br...@yahoo.com>
> One possible solution is setting a .htaccess file for the other root > directories setting the "deny from all" directive to forbid access. > > Pádraic Brady > > http://blog.astrumfutura.com > http://www.survivethedeepend.com > OpenID Europe Foundation Irish Representative<http://www.openideurope.eu/> > > > ------------------------------ > *From:* Alan Wagstaff <awagst...@gmail.com> > *To:* Zend Framework General <fw-general@lists.zend.com> > *Sent:* Monday, January 5, 2009 10:44:37 PM > *Subject:* [fw-general] Project Structure / Public directory > > Hi all, > In most of the ZF tutorials I have read (ZF Quickstart, Rob's one, ZF > Book), they all recommend setting your Apache's webroot to your > /zfapp/public/ directory for security reasons. > > I can understand the logic, putting the application / library directory > outside of the webroot is a good thing but I'm thinking ahead to > distribution and struggling to understand. Take for example, vBulletin - a > popular forum software. When you download vBulletin, you unzip it, grab the > /forum directory and dump it in your webroot. Then visit > http://www.example.com/forum and there's your forum. You could also put > it in /community/forum and it would work just as well. > > I don't really understand how I could do that with ZF using the recommend > project structure. How would I go about setting up my project structure / > .htaccess so the end user could put my app in whatever sub-folder they > wanted on their website, and not just in the webroot? > > Thanks in advance :) > > Alan. > >
