[binarycloud-dev] make configuration

[alex b. <en...@tu...>]

hi all,

I'm building a spec for 'make configuration' and wanted some opinions:

List of Make parameters:

user/site_name/conf/MakeConf.xml
    -Auto-make if make all is called?
    -Site long name
    -Use Zend Encoder?
    -Clean Comments, etc?
    -Standalone or shared binarycloud core?

I could also add:
    -Standalone or shared htdocs?
    -Use Default file set (i.e. if a file doesn't exist in the site tree
that is needed by the system, use the copy of the file from user/default/
---
Any other suggestions?

I suppose we could go haywire and ask for the location to htdocs from build
root, which would allow you to have different "htdocs sets" for different
servers with multiple binarycloud sites..

does anyone think that would be useful?
also, please: any other ideas you can all think of re: make configuration?

Separately, we may want to have Locations (i.e. "if I'm on this hostname,
set docroot and bc root in such a way) - in r1, it was done just by editing
the prepend and adding whatever code you wanted... I'd like to formalize it
through Init in some way. I suppose we could move the code that sets docroot
and bc_path out to a "Locations.php" file in user/site_name/conf/ - but I'm
not sure I like it there or that I like the idea of having the code
separate.

In a perfect world, my preference would be to have a ./configure system that
would be installed both in the source and build tree, with different
purposes:
    -./configure in the source tree would populate the tree with a set of
Makefiles, and configure paths to PHP command line, etc.
    -./configure in the build tree would configure the 'built' installation
to set paths based on rules defined in a php file.

That system would solve any path problems 100%, without incurring overhead
to look at hostname or something on every page render.

opinions welcome...

_a