Book Image

Plone 3.3 Site Administration

Book Image

Plone 3.3 Site Administration

Overview of this book

In the past few years, we have seen some dramatic changes in the way Plone sites are being developed, deployed, and maintained. As a result, developing and deploying sites, changing their default settings, and performing day to day maintenance tasks can be a challenge. This book covers site administration tasks, from setting up a development instance, to optimizing a deployed production site, and more. It demonstrates how-to perform these tasks in a comprehensive way, and walks the user through the necessary steps to achieve results.We have divided the subject of Plone site administration into three categories: development, deployment, and maintenance. We begin by explaining how a Plone site is built, and how to start using it through the web. Next, we add features by installing add-on products, focusing on themes, blogging, and other common enhancements. After the basics of developing and deploying a Plone site are covered, the book covers the basics of maintaining it.Further, throughout the book we preview some new technologies related to Plone site administration, available now as add-ons to the current Plone release. Finally, we will cover a variety of techniques to help you optimize your site's performance.
Table of Contents (15 chapters)
Plone 3.3 Site Administration
Credits
Foreword
About the Author
About the Reviewer
Preface
Index

Understanding the software stack


First, let's review the complex software stack we have created in this chapter.

This is just one of the many scenarios you could deploy within production to handle various types of production environments you may encounter.

Our stack currently looks like this:

In production, it may look like this:

That is to say that in production, you may place a web server like Apache or Nginx in front (on port 80), and then proxy requests to the web server to a web cache like Varnish or Squid, which may then proxy requests down the stack to the Zope 2 instances as needed.

Frontend Apache configuration

In Apache, the proxy configuration typically looks like this (assuming mod_rewrite and mod_proxy have been loaded):

RewriteEngine On
RewriteRule ^(.*) http://127.0.0.1:8080/VirtualHostBase/http/mysite.com:80/Plone/\
  VirtualHostRoot/$1 [P,L]

You will typically find these entries inside a VirtualHost container (but not always).

Frontend Nginx configuration

In Nginx, it typically looks...