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

Automate database packing


Packing the database every month will cause the next daily backup to be a full backup instead of an incremental backup. That is because repozo detects the database change, and performs a full backup as a result.

This is good news for us, because it means that all we have to do to ensure monthly full backups is to configure an automated task to pack the database. In other words, we just require a cron entry in Mac OS X and Ubuntu Linux, and a scheduled task in Windows Task Scheduler.

We will leave the task scheduling to the Windows folks, who can easily create another scheduled task by referring to the steps we performed earlier.

For the Mac OS X and Ubuntu Linux folks, in 05-deployment-maintenance-cron2.cfg we have the following:

[buildout]
extends = 05-deployment-maintenance-cron.cfg
parts += cron2

[cron2]
recipe = z3c.recipe.usercrontab
command = ${buildout:directory}/bin/zeopack
times = 0 0 1 * * 

Notice that we chose a value of 0 0 1 * * for the times parameter...