Re: [binarycloud-dev] make'd site file structure

[Alex B. <en...@tu...>]

> 
> Ok, a few more questions come to mind.
> 
> If I write my core BEFORE I make, this implies that parts of the "source
> tree" need to be accessible by the webserver.  (bindly coding PHP is no
> fun)

No, you run make for changes.
So, modify a file, run make, test.
Make will be quick because it compares fie modification dates.

> When you say "write my code", I assume you mean writing modules.  For
> creating the templates, page definitions, web site directory structure,
> etc requires an existing document root.  It makes sense to me that I can
> simply 'make site_name', then go to my newly make'd site tree, and begin
> coding.

You don't write code in your build directory, you write it in your source
tree. So for example, you'd write some code in
r2/binarycloud/user/site_name/mod/ModuleName.php, and run make.

the webserver would "see" r2/binarycloud/build/en/htdocs/* in a development
environment, probably usr/local/apache/htdocs/en/ in a production
environment.

> Where would my virtual host document point?
> - bc/build/en/site_name
> - /var/www/html/site_name (symlink to bc/build/en/site_name)
> - whatever

Yes.

_a


> ok, that's all i can muster for now..
> jason
> 
> 
> 
> 
> 
> 
> 
> Alex Black wrote:
>> Think of it as:
>> 
>> "source tree" (the place where you write your code)
>> make -> "binary" which is in our case a collection of files which are
>> specifically configured to work with that language context, etc.
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>