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 6. Optimization

If you have made it this far, you should understand how to use Buildout to deploy your site to production by executing specific, production-ready configuration files.

We will not cover any version control systems in this book (for example, RCS, CVS, Subversion, Bazaar, Mercurial, Git), but a brief mention of version control systems in the context of our development and deployment efforts is now in order.

Throughout this book, we have been working with various Buildout configuration files. As a result, you may want to consider the following technique to manage them properly:

  1. Check in buildout's configuration files to Subversion (or a version control system of your choice) when you begin your next project.

  2. Check out the buildout's configuration files to the development environment.

  3. Develop the buildout and commit the results.

  4. Check out the buildout's configuration files to the staging and/or production server.

In the future, technologies like Silver Lining (http://cloudsilverlining...