Hi Steven, thanks a lot for you answer! Is not exactly what I meant cause I didn't explained it very well, but I'll (hopefully) explain it better replying to your email..
On Wed, Oct 22, 2008 at 8:26 PM, Steven Szymczak <[EMAIL PROTECTED]> wrote: > Both the localhost and shared host have the same directory structure, > which is mostly the same as recommended in the docs ok for directory structure, I'm using the same recommended in the docs too. > The absolute path on the shared host is /home/steven/www/site > > And Apache's DocumentRoot is set to /home/steven/www/site/public I saw this is reccomended in the docs too: http://framework.zend.com/manual/en/zend.controller.html#zend.controller.quickstart.go.docroot and also here: http://framework.zend.com/docs/quickstart/set-up-the-project-structure ("We will assume that your web server is running on your local machine and that your public directory is accessible at http://localhost/.";) but this is exactly my problem or better what I'd like to avoid.. as I said I'd like to keep on the same host more than one zend framework project so having for example: /var/www/test/zend/test01/ and /var/www/test/zend/test02/ I'd like to keep DocumentRoot pointed to just /var/www so I'll browse them with: http://localhost/test/zend/test01/ The problem is that I'd like to find out the best and easiest way to set a path prefix to paths I use in views and so on like I wrote on my previous message.. (the guestbook form action url example).. and also for other related things like path to js files like dojo libs and so on.. > Having the DocumentRoot point to the project's "public" dir puts the library > outside of the web root, so you'll always have to call includes using > a relative path like > "include('../library/Zend/Controller/Front.php');". AFAIK, this is > the recommended structure for ZF projects. I see.. for local development this is not a problem for me, for production (the "online" version) I do usually have cPanel shared hosts so I can set files and folder under the public_html folder; in this way I can have the library folder outside the public folder as you suggested (that is a good thing security, and if I'm not wrong you can, as an alternative, also deny everybody accessing the library folder with an .htaccess file if you are allowed to do it) > Making a symlink, within > public/, to the library is a bad idea as it will allow the library > files to be read from the web. what I meant is that wanting to keep more than one project under the same DocumentRoot makes me having more copies of the library folder where I could just keep one for development.. Hope it is more clear now. Thanks. bye, Giovanni.
