[Setup] Plone on the cloud: how to keep it simple but modular ?
toffoli at uni.net
Wed Mar 2 09:48:35 UTC 2011
Thank you Suresh. I will try sticky Nginx.
Thanks also to Alex.
> not sure what you mean by implementation [of the allocation of the Zeo
Yes, I was wondering which is the best way of customizing Buildout for my
case: don't know how to adapt to Plone 4 (blobstorage) the second part of
the following article:
I think that the ZODB must be managed by one ZeoServer, even if it is
extended with a few mount-points. Thus, the current scenario would include:
- sticky Nginx
- ZODB with 2-3 mount-points, one per Plone site
- at least 2 Zeo clients.
As to the Zeo clients, is the hypothesis below reasonable?
- anonymous user: one client per each semi-critical site, one for all the
- authenticated user: one client for all sites.
Thank you again, Giovanni
----- Original Message -----
From: "Suresh V." <suresh_vv at yahoo.com>
To: <setup at lists.plone.org>
Sent: Wednesday, March 02, 2011 2:32 AM
Subject: Re: [Setup] Plone on the cloud: how to keep it simple but modular ?
> Giovanni Toffoli wrote:
>> My questions:
>> - is Nginx + Varnish ok?
> 1. All you need is nginx. You have the correct reference. sticky nginx
> works great.
>> - how to allocate Zeo clients? per site, class of user, both?
>> - how to implement the allocation of the Zeo clients?
> Use a fixed number of ZEO clients and let nginx with sticky handle the
> Setup mailing list
> Setup at lists.plone.org
More information about the Setup