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

Packing your database


Next, we will apply the same basic techniques to another important task—packing your site's database.

In Zope 2, every database transaction is saved. So if you never pack, your database will keep growing and fill up your disk. This is why we must pack; of course, how often you pack will depend on how often your site's content changes.

The recommended strategy is to pack to within seven days of the current date. In other words, keep a week's worth of transactions in the database so that you can restore to as far back as one week, if needed (assuming you are able to use undo successfully).

After you run the 05-deployment-maintenance-production.cfg buildout, you should have a bin/zeopack script.

The default value is to pack to one day. If you want to change that (or the not very commonly used ZEO user/password), you can use the following parameters in the zeo section (which uses the plone.recipe.zope2zeoserver recipe):

  • pack-days: Specifies the number of days for the zeopack...