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

Specifying package versions


We have discussed numerous Buildout recipes in this book, but no Buildout extensions (http://pypi.python.org/pypi/zc.buildout#extensions) until now. A Buildout extension is different from a recipe in a few important ways:

  • Extensions do not define any new sections, whereas recipes are often used within a section (although a section can be defined without a recipe)

  • Extensions are run after Buildout reads its configuration files, but before it executes them

  • Extensions are defined within the buildout section

That being said, you do not need to worry too much about the difference; just be aware of which one you are using.

If you know something is an extension, then it should be defined in the buildout section. If it is a recipe, it should be defined in its own section.

We are going to use the buildout.dumppickedversions (http://pypi.python.org/pypi/buildout.dumppickedversions) extension to help us figure out which package's versions are unspecified (which means effectively...