Overview of production configuration at UW Oshkosh
how we set up our production Plone servers
We use Apache, squid cache, pound load balancing, multiple ZEO clients and multiple ZEO servers.
We have several production hardware boxes: plone1, plone2, plone3. Each of these runs several Zopes, each using a different version of Plone.
We have one hardware box for integration testing: plonedev. We occasionally rsync the Zopes from the production servers over to plonedev so we can check that new products won't misbehave when added to the mix.
SSL encryption is used for all login pages and requests, so that no usernames and passwords are exchanged unencrypted between our server and your browser.
Logins used on our production server authenticate using our email LDAP servers. This gives all our students, faculty, and staff the convenience of logging in using their email username and password.
A Plone site may reside on this production server depending on what sort of information it stores, what custom Plone modules or products it needs, and how much traffic it is likely to receive. If a Plone site uses or stores any confidential information it cannot reside on this shared production server (see the Security document for more information).
Backups of all production Plone sites are performed once daily.











