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

More about Buildout


According to the index page on the Python Package Index (PyPI), (http://pypi.python.org/pypi/zc.buildout/1.5.0b2), Buildout is a:

"System for managing development buildouts"

Since its inception, Buildout has grown to become an elaborate system for building software for both development and production use. You can use it to install a single Python package or a complex application.

Buildout does very little by itself; additional functionality is provided by add-ons called recipes. And with over 200 recipes available from the PyPI, you can use it to do just about anything.

Configuration file format

Buildout's configuration file format is based on the Windows INI-style definition, described here: http://en.wikipedia.org/wiki/INI_file.

If you read the Wikipedia entry here, you will notice INI-style files are made up of parameters of the form name=value.

These parameters are separated by an equals sign (=), and can be grouped into sections of the form [section].

About the Python buildout...