Re: Please Review: Multiple Plone Sites Per Zope Instance Using Separatae Data FS Files For Each One
Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Thats pretty cool.
Just found a bug though. will submit a patch
On 14/03/2009, at 3:59 AM, Anne Bowtell wrote:
> It's also possible to use
>
> collective.recipe.filestorage
>
> [mountpoints]
> recipe = collective.recipe.filestorage
> location = var/filestorage/%(fs_part_name)s/Data.fs
> parts =
> site1
> site2
>
> Anne
>
> mosx86 wrote:
>> Working off the notes in the following documentation:
>> http://plone.org/documentation/how-to/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one/
>> Multiple Plone Sites Per Zope Instance Using Separatae Data FS
>> Files For
>> Each One , and with the help of IanFHood in plone irc, we've put
>> together a
>> working deployment.cfg buildout extension for plone v3.2. It was
>> suggested
>> by <limi> that I post to the documentation group so that the original
>> document is updated.
>>
>>> From the original documentation there were two points that I
>>> became hung up
>> on: First, there is no notation that "zeo-filestorage" needs to be
>> defined
>> in the [buildout] part. Secondly, while whitespace is brought up
>> in the
>> notes, it was unknown to me that all entries after "zeo-conf-
>> additional ="
>> needed to begin with whitespace. These may both be novice mistakes
>> on my
>> part, but it would help to clarify them or provide a link back to
>> documentation should it exist.
>>
>> The major changes that we made from the documented method in the
>> notes are
>> as follows:
>>
>> 1. Define zeo-filestorage in [buildout]
>>
>> [buildout]
>> ...
>> zeo-filestorage = ${buildout:directory}/var/filestorage
>>
>>
>> 2. Use ${buildout:directory} in my var declarations for each
>> zeoclient
>> configuration within each zodb_db element:
>>
>> <zeoclient>
>> ...
>> var ${buildout:directory}/var
>> </zeoclient>
>>
>> 3. Call the zope-conf-additional settings from [instance] into
>> [debug-instance]
>>
>> [debug-instance]
>> ...
>> zope-conf-additional = ${instance:zope-conf-additional}
>>
>> It may also be worthwhile to discuss potential performance issues
>> with such
>> a setup. Please let me know if you need any further details.
>>
>> Regards!
>>
>> http://n2.nabble.com/file/n2470168/deployment.cfg deployment.cfg
>>
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM)
> are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
> and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based
> development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com