making them relative is probably the best option
for portability and maintainability...
that way, you can change the underlying directory
structure and not have to change any of the actual
code... it's great if you ever have to change
servers, or if the directory structure undergoes
any structural changes in the future.
> -----Original Message-----
> From: Aaron Bennett [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 2:33 PM
> To: php
> Subject: [PHP] .htaccess php_value
>
>
> Hi There,
> I currently use .htaccess files to override the include path, which works
> great for me... One of my concerns was the portability of the code, and the
> possibility of not having control of http.conf....
>
> I'm now in the process of porting some of the sites onto a winnt architecure
> (but still using apache as my webserver...). The contents of some of these
> .htaccess files looks simelar to:
>
> php_value include_path
> ".:/home/www/htdocs/php-lib:/home/www/htdocs/includes"
>
> unfortunatly, apache for windows would prefer the format somewhat like:
>
> php_value include_path ".;c:\web\site\php-lib;c:\php\whatever\includes"
>
> (note the use of ';' rather than ':' as well)
>
> So my question, is whats the best way to make the site's as portable as can
> be? I assume that i could go thru _all_ the code and make include references
> relative rather than relying on the config to find include()'s.... Any
> suggestions?
>
> --
> Aaron Bennett
> [EMAIL PROTECTED]
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
