hi all,
for the distro version of r2, I want to get to the point where a user can
download the system, untar it, point their browser to it, and have a
functioning installation.
the instructions should consist of:
-untar
-binarycloud/user/conf/datasources.xml
-cd binarycloud make
-./Makefile
point browser at:
/path/to/bc/files/in/htdocs/index.php
-----
along those lines,
I'm going to build a very simple little file called
binarycloud.php
which will be included from each page in htdocs:
include_once('binarycloud.php');
note the "pathlessness" - i.e. binarycloud.php will be in your include_path.
the idea behind this is to set the constant BC_PATH before anything else
happens, but to avoid using prepends, etc to get that working.
this also has a number of other advantages like the ability to have many
virtualhosts use the same cvs checkout of a binarycloud install, etc.
my question:
-does anyone know of a reason why
$HTTP_SERVER_VARS[DOCUMENT_ROOT]
would _not_ work as a basis for setting up BC_PATH?
I don't have access to iPlanet, etc, so I can't check that the above var
is useful on other server platforms besides apache.
i.e.
<?php
$pieces = explode('/', $HTTP_SERVER_VARS[DOCUMENT_ROOT]);
$count = count($pieces);
$cd_up = 1;
for ($i=1; $i <= $count-$cd_up; $i++) {
$path .= '/'.$pieces[$i];
}
$path .= '/binarycloud';
define('BC_PATH',$path);
echo BC_PATH;
?>
would be the contents of the binarycloud.php include.
_alex
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|
