link each site to a single file which
sets the $inc_root, so you only change one file.
HTH
Peter
-Original Message-
From: mike [mailto:[EMAIL PROTECTED]
Sent: 13 November 2003 14:42
To: [EMAIL PROTECTED]
Subject: [PHP-DB] using code for multiple sites
I currently manage
I currently manage several websites that share the same code.
This code is included into many of the pages on every site.
I have duplicate copies of the code set up in each virtual host
directory.
Obviously this wastes space on my server and wastes my time having to
update them all.
I was
13, 2003 3:42 PM
To: [EMAIL PROTECTED]
Subject: [PHP-DB] using code for multiple sites
I currently manage several websites that share the same code. This code
is included into many of the pages on every site. I have duplicate
copies of the code set up in each virtual host directory. Obviously
- Original Message -
From: mike [EMAIL PROTECTED]
I currently manage several websites that share the same code.
create a directory called inc in /usr/local/apache
and then add the following line to php.ini
include_path = .:/usr/local/apache/inc
I'd use a method like this, although
]
Sent: 13 November 2003 14:42
To: [EMAIL PROTECTED]
Subject: [PHP-DB] using code for multiple sites
I currently manage several websites that share the same code.
This code is included into many of the pages on every site.
I have duplicate copies of the code set up in each virtual host
directory
create a directory called inc in /usr/local/apache
and then add the following line to php.ini
include_path = .:/usr/local/apache/inc
I'd use a method like this, although I'd probably just use an absolute path
instead of adjusting the include_path.
What's the benefit of using an absolute
From: Chris Boget [EMAIL PROTECTED]
create a directory called inc in /usr/local/apache
and then add the following line to php.ini
include_path = .:/usr/local/apache/inc
I'd use a method like this, although I'd probably just use an absolute
path
instead of adjusting the include_path.
