binarycloud-dev

[binarycloud-dev] make configuration

[alex b. <en...@tu...>]

hi all,

I'm building a spec for 'make configuration' and wanted some opinions:

List of Make parameters:

user/site_name/conf/MakeConf.xml
    -Auto-make if make all is called?
    -Site long name
    -Use Zend Encoder?
    -Clean Comments, etc?
    -Standalone or shared binarycloud core?

I could also add:
    -Standalone or shared htdocs?
    -Use Default file set (i.e. if a file doesn't exist in the site tree
that is needed by the system, use the copy of the file from user/default/
---
Any other suggestions?

I suppose we could go haywire and ask for the location to htdocs from build
root, which would allow you to have different "htdocs sets" for different
servers with multiple binarycloud sites..

does anyone think that would be useful?
also, please: any other ideas you can all think of re: make configuration?

Separately, we may want to have Locations (i.e. "if I'm on this hostname,
set docroot and bc root in such a way) - in r1, it was done just by editing
the prepend and adding whatever code you wanted... I'd like to formalize it
through Init in some way. I suppose we could move the code that sets docroot
and bc_path out to a "Locations.php" file in user/site_name/conf/ - but I'm
not sure I like it there or that I like the idea of having the code
separate.

In a perfect world, my preference would be to have a ./configure system that
would be installed both in the source and build tree, with different
purposes:
    -./configure in the source tree would populate the tree with a set of
Makefiles, and configure paths to PHP command line, etc.
    -./configure in the build tree would configure the 'built' installation
to set paths based on rules defined in a php file.

That system would solve any path problems 100%, without incurring overhead
to look at hostname or something on every page render.

opinions welcome...

_a

Re: [binarycloud-dev] make configuration

[jason <ja...@gr...>]

I'll propose a potential concern here. i'm not sure how HTTPS/SSL is
handled (site level vs. page level), but if the secure hostname/path
differs from the non-secure hostname/path, make may need to know this at
build time.

For example:
if only the checkout portion of a site is SSL enabled, and it's moved to
a seperate docroot to keep visitors from viewing the rest of the site
encrypted, one may want just the checkout.php to sit elsewhere


http://mysite.com -> /var/www/html/mysite.com/
   which has shop.php (categories.php, specials.php, etc etc)
https://mysite.com -> /var/www/html/secure/mysite.com/
   which only has checkout.php


This may be a bit too oddball for BC to support.  _shrug_

jason



alex black wrote:
> I'm building a spec for 'make configuration' and wanted some opinions:
> Any other suggestions?

Re: [binarycloud-dev] make configuration

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

> I'll propose a potential concern here. i'm not sure how HTTPS/SSL is
> handled (site level vs. page level), but if the secure hostname/path
> differs from the non-secure hostname/path, make may need to know this at
> build time.

The hostname couldn't be different (it's not the "virtual name" hostname is
single and unchangeaable...) but paths could definitely change, and that is
a good point.

> For example:
> if only the checkout portion of a site is SSL enabled, and it's moved to
> a seperate docroot to keep visitors from viewing the rest of the site
> encrypted, one may want just the checkout.php to sit elsewhere
> 
> 
> http://mysite.com -> /var/www/html/mysite.com/
>  which has shop.php (categories.php, specials.php, etc etc)
> https://mysite.com -> /var/www/html/secure/mysite.com/
>  which only has checkout.php

>
> This may be a bit too oddball for BC to support.  _shrug_

But now that I think about it, what prevents you from having this tree?:

user/site_name/htdocs/
                    secure/
                    base/

doing a make 'like normal' and just setting your virtualhosts accordingly?

...

I'm trying to think of holes in that theory :)

_a

Re: [binarycloud-dev] make configuration

[Jason H. <jc...@ey...>]

Well, here is our company's current SSL virtual host setup.  While it's
not perfect, (it's actually cheap), it may need to be considered as a
possible BC configuration concern.


Say we host 10 sites on one server, all with their own vhost/docroot. 
For SSL, there is a vhost/docroot pointing to
secure.domain.com/site_name.  This allows us to secure multiple sites
under one certification.

So if the site is:
http://www.site_name.com  == /var/www/html/site_name

the secured pages would be located at:
https://secure.companyname.com/site_name   ==
/var/www/html/secure/site_name

Told ya it was cheap. :p

jason




Alex Black wrote:
> 
> > I'll propose a potential concern here. i'm not sure how HTTPS/SSL is
> > handled (site level vs. page level), but if the secure hostname/path
> > differs from the non-secure hostname/path, make may need to know this at
> > build time.
> 
> The hostname couldn't be different (it's not the "virtual name" hostname is
> single and unchangeaable...) but paths could definitely change, and that is
> a good point.
> 
> > For example:
> > if only the checkout portion of a site is SSL enabled, and it's moved to
> > a seperate docroot to keep visitors from viewing the rest of the site
> > encrypted, one may want just the checkout.php to sit elsewhere
> >
> >
> > http://mysite.com -> /var/www/html/mysite.com/
> >  which has shop.php (categories.php, specials.php, etc etc)
> > https://mysite.com -> /var/www/html/secure/mysite.com/
> >  which only has checkout.php
> 
> >
> > This may be a bit too oddball for BC to support.  _shrug_
> 
> But now that I think about it, what prevents you from having this tree?:
> 
> user/site_name/htdocs/
>                     secure/
>                     base/
> 
> doing a make 'like normal' and just setting your virtualhosts accordingly?
> 
> ...
> 
> I'm trying to think of holes in that theory :)
> 
> _a
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev

Re: [binarycloud-dev] make configuration

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

No concern, you can do that now.

Just run a symlink from
build/site_name/en/htdocs/secure to /var/www/html/secure/site_name
and
build/site_name/en/htdocs/base (or whatever) to /var/www/html/site_name

:)

_a

> Well, here is our company's current SSL virtual host setup.  While it's
> not perfect, (it's actually cheap), it may need to be considered as a
> possible BC configuration concern.
> 
> 
> Say we host 10 sites on one server, all with their own vhost/docroot.
> For SSL, there is a vhost/docroot pointing to
> secure.domain.com/site_name.  This allows us to secure multiple sites
> under one certification.
> 
> So if the site is:
> http://www.site_name.com  == /var/www/html/site_name
> 
> the secured pages would be located at:
> https://secure.companyname.com/site_name   ==
> /var/www/html/secure/site_name
> 
> Told ya it was cheap. :p
> 
> jason
> 
> 
> 
> 
> Alex Black wrote:
>> 
>>> I'll propose a potential concern here. i'm not sure how HTTPS/SSL is
>>> handled (site level vs. page level), but if the secure hostname/path
>>> differs from the non-secure hostname/path, make may need to know this at
>>> build time.
>> 
>> The hostname couldn't be different (it's not the "virtual name" hostname is
>> single and unchangeaable...) but paths could definitely change, and that is
>> a good point.
>> 
>>> For example:
>>> if only the checkout portion of a site is SSL enabled, and it's moved to
>>> a seperate docroot to keep visitors from viewing the rest of the site
>>> encrypted, one may want just the checkout.php to sit elsewhere
>>> 
>>> 
>>> http://mysite.com -> /var/www/html/mysite.com/
>>>  which has shop.php (categories.php, specials.php, etc etc)
>>> https://mysite.com -> /var/www/html/secure/mysite.com/
>>>  which only has checkout.php
>> 
>>> 
>>> This may be a bit too oddball for BC to support.  _shrug_
>> 
>> But now that I think about it, what prevents you from having this tree?:
>> 
>> user/site_name/htdocs/
>>                     secure/
>>                     base/
>> 
>> doing a make 'like normal' and just setting your virtualhosts accordingly?
>> 
>> ...
>> 
>> I'm trying to think of holes in that theory :)
>> 
>> _a
>> 
>> _______________________________________________
>> binarycloud-dev mailing list
>> bin...@li...
>> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>