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

Analyzing the contents of our buildout


In this book, we have created a fairly large buildout, spread across many files. As a result, perhaps you are wondering what it would look like if the same buildout were contained in a single file?

We answer that question in 08-future-final.cfg, which contains the following sections, parameters, and values, presented here along with some commentary about each:

  • Every buildout must define a buildout section:

    [buildout]
  • By assigning parameters from various versions sections to the versions parameter in the buildout section, we are able to specify package version numbers:

    versions = versions
  • Every buildout section must have a parts parameter (even if it is empty):

    parts = 
        zope2
        instance
  • In Chapter 2, Site Basics, we introduced the collective.recipe.plonesite recipe (http://pypi.python.org/pypi/collective.recipe.plonesite) configured in a section called plonesite:

    # Chapter 2
        plonesite
  • In Chapter 3, Appearance, we introduced the collective.recipe.omelette...