Re: [binarycloud-dev] Suggestion for multiple sites

[Justin F. <je...@ey...>]

Jimmy:

There is a discussion going on to change from:
user
|-- binarycloud
|   `-- mod
|       `-- mod
|           `-- xslt_example
|-- conf
|-- db
|   |-- dump
|   `-- schema
|-- lang
|-- mod
|   |-- astronomy
|   |-- hello_world
|   |-- lib
|   |-- myCP
|   |-- set_lang_example
|   |   `-- html
|   |-- system
|   |-- test
|   |-- webalizer
|   |   `-- webalizer
|   `-- xslt_example
|-- roles
`-- tmpl
    `-- html
        |-- layouts
        `-- masters

in which site-specific modules and/or general modules have
to go under user/mod, and/or site-specific masters and
layouts, to avoid name clash, have to be under

|-- roles
`-- tmpl
    `-- html
        |-- layouts/site_name
        `-- masters/sites_name

TO----------

sites to be put at the ./user level, like

user
|-- binarycloud
|   `-- mod
|       `-- mod
|           `-- xslt_example
|-- conf
|-- db
|   |-- dump
|   `-- schema
|-- lang
|-- mod
|-- roles
`-- tmpl
|   `-- html
|       |-- layouts
|       `-- masters
site1
|-- conf
|-- lang
|-- mod
`-- tmpl
|    `-- html
|       |-- layouts
|       `-- masters
|
site2
|

and so forth.  This makes BC more multi-site friendly.
Anyway, this is what I understand what is being considered.

Right now, I just am developing all modules under
"package" directories under ./mod/package and
have all masters/layouts in the same directory
but pay attention not to have name clash, even
though masters and layouts will be numerous
over many sites.  I hope this will be temporary.

There has also been a discussion of the DOCUMENT_ROOT
tree structure, but, in a way, this is up to the
user and BC doesn't need to dictate how the DOCUMENT_ROOT
is organized, it is truly a user preference.

-------------------------

Jimmy Harlindong wrote:
> 
> Odysseas / alex,
> 
> Perhaps to make BC multi site friendly we can do it like this:
> 
> /path/to/binarycloud/user/siteA
> /path/to/binarycloud/user/siteB
> /path/to/binarycloud/user/siteC
> 
> Move everything under
> /path/to/binarycloud/user
> Into
> /path/to/binarycloud/user/siteA
> 
> Then on the make command it would be:
> 
> make siteA
> 
> Or to build a site skeleton:
> make new name=siteA
> 
> Perhaps the skeleton should be placed under:
> /path/to/binarycloud/base/skeleton
> 
> Regards,
> Jimmy Harlindong
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev

-- 
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722