Joined: 21 Apr 2005 |
Posts: 9 |
|
|
 |
Posted: Mon Apr 25, 2005 11:54 am |
|
 |
 |
 |
 |
How should the mappings be set up if the Top Publishing Directory doesn't correspond to the Remote Root Directory?
For example, suppose I want to store some library files (with passwords, say) outside of the html directory, so those files are not accessible on the Internet.
So on the remote webserver, the Top Publishing Directory is like: /home/test/
Libraries go in /home/test/inc/
and the html directory is /home/test/html/
On my local machine, the Project Root Directory is like: /home/me/projects/test/
The remote url is like http://myserver/
Thus, when I download the project files from the remote server, I end up with the libraries in /home/me/projects/test/inc, and the html files in /home/me/projects/test/html
However, when I try to execute the home page file /home/me/projects/test/html/index.php, the URL that gets opened in the browser is http://myserver/html/index.php
Of course, the browser cannot find this file (because it is at http://myserver/index.php) and returns an error.
I've tried every combination possible, but I can't get the debugger to leave off that darn 'html' subdirectory. Is it impossible to set this up?
If I set up the mappings so they are zeroed in on the html directory only, everything works fine, but then I can't edit anything outside of the html directory. This isn't very practical.
Do I need to set up two project? One at the /home/test level for editing and one at the /home/test/html level for debugging??? This is the only work around I can think of, but it seems awkward.
Any help much appreciated.
-- John
|
|