Sam Tregar wrote:
>On Sun, 17 Feb 2002, Chris Hamilton wrote:
>
>>Hmm, I am not sure this would work well for my situation.
>>
>>Each DB for bricolage takes 10MB just to set up, so I am thinking it
>>might not be good to try it the way I was thinking as well.
>>
>
>I don't think I understand what you're driving at here. I thought you
>were asking if it was possible to setup separate Bricolage instances
>inside a single Apache server using virtual hosts. In such a setup each
>Bricolage instance would still need its own database. I don't think
>separate Bricolage instances are ever going to be able to share a databse,
>but maybe that's not what you meant?
>
What I meant was that I don't want to allocate 10MB for each instance. I
want the
system as light as possible. See below...
>
>>I have been playing with the permissions for admin. Would there be a
>>way to give virtual hosters complete administration over a category or
>>something. Let them add users, etc. as if they were the full admin, but
>>have their changes and all things they do only influence their
>>directory? This way would also be good for the real admin as then they
>>could have complete access to help the virtual admin if required.
>>
>
>Category level permissions are definitely something I think we should add
>to the system. We're already planning to allow permissions to control
>visbility - i.e. if you can't access something then you don't see it at
>all. Combining the two you might end up with a system where multiple
>disparate groups of users could cohabitate in one Bricolage instance
>without tripping over each other.
>
>However, nothing we're currently planning has anything to do with virtual
>hosts... Could you explain what you're proposing in more detail? I get
>the sense I'm missing the point.
>
>-sam
>
Sure, sorry I am confusing you. I would like to add bricolage as a
hosting option on my
server. I would like to add it as a CMS system for client users (each
user being content independent
and secured from other users). I would make it so the resulting
production pages appear on the
users virtual host.
The development/preview can be done on a single host as long as the
users are unique. Right now I
am giving each user account a system account. Under a system like
bricolage there would
also be virtual users authorized by the system account while acting as
the virtual admin.
Clients under our hosting could then have whoever they like work on
their content, etc..
The virtual hosts could be something as simple as resulting directories
of the publishing root I think.
Then each system account just has their own 'category' under the main
system.
So they would be on:
Bricolage server:
bri.here.com.sg
Preview directory:
bri.here.com.sg/example.com/ -> /var/www/preview/example.com
Production:
www.example.com -> /var/www/production/example.com
Virtual admin: name or example.com
Virtual users: name@example.com
This would keep everything in one DB and not overload the system hopefully.
I'll poke around and see if I have a clue as to how to go about this.
Any major changes between
development and stable that would touch this area?
I am just looking to integrate it into small hosting biz as cheaply and
secure as possible. I want it to
be cheap for clients to use as well.
Thanks,
-Chris
_______________________________________________
Bricolage-Devel mailing list
Bricolage-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-devel