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

Upgrading to Plone 4


It is now time to explore upgrading to Plone 4.

Nowadays, as far as the software itself is concerned, this is a relatively simple process.

Especially as far as our buildout.cfg file is concerned, it is simple.

At the time of this writing, Plone 4 is just about to release its first release candidate. This means that we can experiment with the most recent beta release—beta 3.

For Plone 4 beta 3's versions.cfg file, visit http://dist.plone.org/release/4.0b3/versions.cfg.

Even though we have already specified a versions.cfg, we can specify another one, because Buildout will just use the last specified value for each parameter.

In the case of a versions section that looks like as shown, Buildout will use the latter version:

[versions]
Plone = 3.3.5
Plone = 4.0b3

Effectively, extending the Plone 4 beta 3 versions.cfg file and executing Buildout upgrades your software stack (but not your database) to Plone 4 beta 3.

There are a few additional concerns we must address before you do...