No.... not exactly.
The build URL is the path you want your pages built in. It's not the "home" url. It's the URL page.cgi uses to determine where the build_path built the static pages -- or would have. It's the URL to the build_path, and the logical top of the Links directory.
This should not PHYSICALLY map onto the top of your server directory, which is why it's suggested to use Links or Links/Pages as the place to put the directory.
There have been numerous warnings about using "/" (the root server directory) as the build path. It's a security hole, at the very least. Always use a subdirectory, then use redirects, .htaccess files or even symlinks to alias your root URL (http://servername.com) to the subdirectory. You really don't want your root directory writable by world, or the server.
The build path, is the path to the url used above, where the actual pages are built by build.pm. You access this physical path via the webserver using the build_URL.
Another way to look at this is that the URL is how the webserver knows where the physical server built the pages. When you want to get to your system via the web (as admin or as user) you need an http:// path. When the programs are running on the server, they do not know about http:// paths, but need a physical, absolute (or relative) path to follow on the file system.
Hope this helps, but might just have added to the confusion ;)
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
The build URL is the path you want your pages built in. It's not the "home" url. It's the URL page.cgi uses to determine where the build_path built the static pages -- or would have. It's the URL to the build_path, and the logical top of the Links directory.
This should not PHYSICALLY map onto the top of your server directory, which is why it's suggested to use Links or Links/Pages as the place to put the directory.
There have been numerous warnings about using "/" (the root server directory) as the build path. It's a security hole, at the very least. Always use a subdirectory, then use redirects, .htaccess files or even symlinks to alias your root URL (http://servername.com) to the subdirectory. You really don't want your root directory writable by world, or the server.
The build path, is the path to the url used above, where the actual pages are built by build.pm. You access this physical path via the webserver using the build_URL.
Another way to look at this is that the URL is how the webserver knows where the physical server built the pages. When you want to get to your system via the web (as admin or as user) you need an http:// path. When the programs are running on the server, they do not know about http:// paths, but need a physical, absolute (or relative) path to follow on the file system.
Hope this helps, but might just have added to the confusion ;)
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
