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

Chapter 5. Deployment and Maintenance

This chapter marks a significant turning point for us in this book. Up until now, we have only discussed development issues (more or less). For the next four chapters, we will only discuss deployment/maintenance issues (more or less).

Do you remember the site administration diagram, located at the beginning of Chapter 1? A fair amount of development tasks have now been covered, so we can now switch to deployment/maintenance tasks with confidence, knowing that we understand what the various development tasks look like. Also, remember that in the real world, you are likely to have deployed to staging numerous times before deploying to production.

In a way, you have already been prepared for what is coming next. By demonstrating Buildout's ability to extend configuration files, we have (hopefully) shown that a production buildout is just a buildout configuration file(s) that configures the site for production use.

In some cases, a production buildout may get...