[Setup] multiple plone sites: need advice on how to set up

Peter Simmons pete-lists at bcmpweb.com
Sat Jul 1 02:27:36 UTC 2006


You need to give the 2 databases different mount points but everything 
else is the same.

I.e. Data1.fs mount /
i.e. Data2.fs mount /data2

What we usually do (you are welcome to do what you want) is to leave 
default main entry alone, i.e. Data.fs mount /

And add extras E.g.

<zodb_db client1>
       # client1 FileStorage database
       <filestorage>
         path $INSTANCE/var/client1_Data.fs
       </filestorage>
       mount-point /client1
   </zodb_db>

<zodb_db client2>

       # client2 FileStorage database
       <filestorage>
         path $INSTANCE/var/client2_Data.fs
       </filestorage>
       mount-point /client2
   </zodb_db>


Cheers,
Pete
Stuart L. Marshall wrote:
> I've looked and it says:
>
> ---------------------------------------------------------------------
>    # Database (zodb_db) section
>    #
>    # Description:
>    #     A database section allows the definition of custom database
>    #     and
>    #     storage types.  More than one zodb_db section can be defined.
>    #
>    # Default: unset.
>    #          IMPORTANT: At least one database with a mount-point of
>    #          "/"
>    #          must be specified for Zope to start properly.
>
>    <zodb_db main>
>        # Main FileStorage database
>        <filestorage>
> 	 path $INSTANCE/var/Data.fs
>        </filestorage>
>        mount-point /
>    </zodb_db>
>
>    <zodb_db temporary>
>        # Temporary storage database (for sessions)
>        <temporarystorage>
> 	 name temporary storage for sessioning
>        </temporarystorage>
>        mount-point /temp_folder
>        container-class Products.TemporaryFolder.TemporaryContainer
>    </zodb_db>
> ---------------------------------------------------------------------
>
> Now please keep in mind I have not done this before!
>
> If I want to have 2 Data.fs files, say Data1.fs, Data2.fs
> it is not clear what to do.  I can write:
>
>    <zodb_db main1>
>        # Main FileStorage database
>        <filestorage>
>          path $INSTANCE/var/Data1.fs
>        </filestorage>
>        mount-point /
>    </zodb_db>
>
>    <zodb_db main2>
>        # Main FileStorage database
>        <filestorage>
>          path $INSTANCE/var/Data2.fs
>        </filestorage>
>        mount-point /
>    </zodb_db>
>
> But then what happens in the zope management interface when I
> go to create a plone site?  How do I associate one with Data1.fs
> and the second with Data2.fs.
>
> I did not find any definitive examples or explanation of this in
> the zope documentation.
>
> I have not tried to start zope with this config yet, but will
> shortly.
>
> thanks,
> Stuart
>
>
> Quoting Alan Runyan (alan at enfoldsystems.com) on Fri, Jun 30, 2006 at 01:48:01PM -0500:
>   
>> Look at your zope.conf
>>
>>  Alan Runyan
>>  Enfold Systems, Inc.
>>  http://www.enfoldsystems.com/
>>  phone: +1.713.942.2377x111
>>  fax: +1.832.201.8856
>>
>>  
>>
>>     
>>> -----Original Message-----
>>> From: Stuart L. Marshall [mailto:marshall at slac.stanford.edu] 
>>> Sent: Friday, June 30, 2006 1:46 PM
>>> To: Alan Runyan
>>> Cc: Daniel Melnechuk; Stuart L. Marshall; Setup at lists.plone.org
>>> Subject: Re: [Setup] multiple plone sites: need advice on how 
>>> to set up
>>>
>>> Thanks very much for the help.  
>>>
>>> If I search the zope docs, will I find these mount-point facilities?
>>> I did not see them in the "add a plone site" sequence on my 
>>> older zope installation but I am about to go to zope 2.9 on a 
>>> fresh install.
>>>
>>> Stuart
>>>
>>> Quoting Alan Runyan (alan at enfoldsystems.com) on Fri, Jun 30, 
>>> 2006 at 01:34:45PM -0500:
>>>       
>>>> We run multiple Plones per Zope install.
>>>>
>>>> The best approach is to use Zope's mount-point facilities for each 
>>>> Plone.
>>>> Thus you can control the ram utilizations and apply zodb 
>>>>         
>>> policies per 
>>>       
>>>> Plone; i.e. mount each Plone site.
>>>>
>>>> On Plone.org we mount the portal_catalog since that has a 
>>>>         
>>> distinctly 
>>>       
>>>> different usage policy (i.e. we have catalog's mount point 
>>>>         
>>> caching 40k 
>>>       
>>>> objects or so -- we load a lot of the catalog into memory).
>>>>
>>>> cheers
>>>>  Alan Runyan
>>>>  Enfold Systems, Inc.
>>>>  http://www.enfoldsystems.com/
>>>>  phone: +1.713.942.2377x111
>>>>  fax: +1.832.201.8856
>>>>
>>>>  
>>>>
>>>>         
>>>>> -----Original Message-----
>>>>> From: Daniel Melnechuk [mailto:isis at isisdesign.com]
>>>>> Sent: Friday, June 30, 2006 1:07 PM
>>>>> To: Alan Runyan
>>>>> Cc: Stuart L. Marshall; Setup at lists.plone.org
>>>>> Subject: Re: [Setup] multiple plone sites: need advice on 
>>>>>           
>>> how to set 
>>>       
>>>>> up
>>>>>
>>>>> Alan,
>>>>>
>>>>> Sorry to be nag, but what you said is not exactly clear. 
>>>>>           
>>> The second 
>>>       
>>>>> line seems to imply each plone should have its own Zope. But your 
>>>>> first line seems to imply that you should put all Plones into one 
>>>>> Zope.
>>>>>
>>>>> Could you please expand on your opinion as to one plone 
>>>>>           
>>> per zope or 
>>>       
>>>>> many plones per zope?
>>>>>
>>>>> Peace,
>>>>> Dan
>>>>>
>>>>>
>>>>> On Jun 30, 2006, at 12:32 PM, Alan Runyan wrote:
>>>>>
>>>>>
>>>>> 	Run multiple plone sites in a zope instance.
>>>>>
>>>>> 	Each plone site should have its own mount point.
>>>>>
>>>>> 	\
>>>>>
>>>>> 	
>>>>> 	
>>>>>
>>>>> 	 Alan Runyan
>>>>>
>>>>> 	 Enfold Systems, Inc.
>>>>>
>>>>> 	 http://www.enfoldsystems.com/
>>>>>
>>>>> 	 phone: +1.713.942.2377x111
>>>>>
>>>>> 	 fax: +1.832.201.8856
>>>>>
>>>>> 	
>>>>> 	
>>>>>
>>>>>
>>>>>
>>>>>           
>>> Content-Description: Alan Runyan.vcf
>>>
>>>
>>> -- 
>>> - Stuart Marshall       650 926 3616                Office
>>> - KIPAC/SLAC M/S 29         926 4310                Dept Office
>>> - 2575 Sand Hill Rd.        926 5566                FAX
>>> - Menlo Park, CA 94025  marshall at slac.stanford.edu  E-mail
>>>
>>>       
>
> Content-Description: Alan Runyan.vcf
>
>
>   




More information about the Setup mailing list