binarycloud-dev

[binarycloud-dev] multi-site makes

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

hi all,

I'm thinking about doing multi-site makes this way.
This is very, very early thinking so please bear that in mind :)

-----

The current contents of binarycloud/user/ is moved into
binarycloud/user/default/ (default would be the "default" distro site name)

With the idea being that you end up with:

binarycloud/
    user/
        default/
            ** current contents of binarycloud/user/* **
        site_name/
        other_site/
        smallsite/
        bigsite/
        blah/
        blah/
        blah/

Also, I would like to try and structure the makefile so there is only one,
top level user/Makefile - I don't want to have to maintain (x) Makefiles, or
a directory of directories ala:

SITE_DIRS =             \
            site_name   \
            other_site  \
            blah        \

etc.

Right now, there is explicit declaration of the _internal_ structure of the
user/ tree:

USERDIRS=               \
                conf    \
                db      \
                lang    \
                lib     \
                mod     \
                roles   \
                tmpl    \
        $(EMPTY)

So, what I was thinking...

We enforce this structure within


binarycloud/
    user/
        site_name/

_but_ - if there is a missing directory from binarycloud/user/site_name/,
we'd grab user/default/missing_directory_name/ and include it in the build
version of binarycloud/user/site_name/

So, for example, you could leave out the user/site_name/conf/ directory, and
know that it would be grabbed from user/default/conf/ at make-time and put
in user/site_name/conf/. That would be great for maintaining a 'base'
config.

I need to do a little more looking + putzing, but I think this may be
possible at the file level for important files that reside in: conf/ and
lang/, also.


best,

_alex





--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093

RE: [binarycloud-dev] multi-site makes

[Andreas A. <a.a...@th...>]

Hi Alex,

> I'm thinking about doing multi-site makes this way.
> This is very, very early thinking so please bear that in mind :)

-----

> The current contents of binarycloud/user/ is moved into
> binarycloud/user/default/ (default would be the "default" distro site
name)
Sounds good to me.


> binarycloud/
>     user/
>         default/
>             ** current contents of binarycloud/user/* **
>         site_name/
>         other_site/
>         smallsite/

I like that organization MUCH more than the

binarycloud/
	user/
	site_1/
	site_2/
	site_3/

you suggested earlier. Ist clear an you will have user/default/ and
user/site_name/ in the build tree. That feels natural to me.


> Also, I would like to try and structure the makefile so there is only one,
> top level user/Makefile - I don't want to have to maintain (x) Makefiles,
or
> a directory of directories ala:

Right, that's a mess. But that requires strict obedience to the directory
structure at least in /user/sitename/*, why not? This ensures that maybe
people could share whole sites without trouble.


>binarycloud/
>    user/
>        site_name/

> _but_ - if there is a missing directory from binarycloud/user/site_name/,
> we'd grab user/default/missing_directory_name/ and include it in the build
> version of binarycloud/user/site_name/

Wow, thats cool.


> So, for example, you could leave out the user/site_name/conf/ directory,
and
> know that it would be grabbed from user/default/conf/ at make-time and put
> in user/site_name/conf/. That would be great for maintaining a 'base'
> config.

Ok, but that mechanism should also work for individual files not only for
the directories.

All in all I like this organization. It's clear and self explaining.

Andi