Re: [binarycloud-dev] Suggestion for multiple sites

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

> 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
> |

Actually, I was thinking one level below in the source tree.

In the build tree, the imports would probably looks like

sitename.mod.mod_dir.ModuleName

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

Not considered, many people have mentioned this and I totally agree with it.

After core is complete and stable, we'll go through and do this "other
stuff"

> 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.

It will.

> 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.

yes, the only "requirement" for distro modules is that they use the
resources/ tree.


-alex