RE: [binarycloud-dev] RE: r2 /make

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

Hi Alex,

>> r2/binarycloud/build/binarycloud/
>> r2/binarycloud/build/htdocs/
>> Why that ?
> because
> /path/to/r2/binarycloud/base/*
> is the source tree, it is not used in production.
ok, thats clear

> if you look in build/en/binarycloud/* you'll notice that the organization
is
> different.
Yepp. But I don't get it right now how the build arch is handled with the
webserver config.

If I understand right the language rips are completly standalone systems.
Thats good and no problem if you have different docroots/vhosts vor each
language. e.g.

foo.com points to build/htdocs/  -> determines language and switches to
en.foo.com points to build/en/htdocs or
de.foo.com points to build/en/htdocs
etc.

but what if you want to have language switching capabilities within one site
e.g. foo.com and foo.de points to the same docroot:

foo.com -> derminte language and set internally
user switches foo.com?.lang=de

or another organization:
foo.com/de/
foo.com/en/

How is this handled within the build-tree. I only want the htdocs directory
accessible by the user. The directories above should be out ouf user scope.

Maybe this is a stupid question and I'm missing something obvious. But I
don't get it right now :-(

.andi


--
When we eliminate the impossible, whatever remains,
however improbable, must be true. -- Sherlock Holmes