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

Executing Buildout in offline mode


Specifying package versions is critical to creating a KGS.

So, what happens if the Internet goes down and/or you are unable to reach http://dist.plone.org/release/3.3.5/versions.cfg?

For this, we have two approaches.

The first, newer approach is to use Buildout's extends cache feature, information about which is available on http://pypi.python.org/pypi/zc.buildout#caching-extended-configuration We will not cover that here, but it is probably worth a look.

In the worst-case scenario though, you can try the following approach.

Inside the code bundle in the versions.cfg file, we have included the contents of http://dist.plone.org/release/3.3.5/versions.cfg.

In the event you lose connectivity, or you want to deploy to an environment sans Internet, you need two things:

  • The packages themselves (which reside in the eggs directory)

  • Their version specifications

We already included version specifications for our add-on packages in 08-future-versions.cfg, which we discovered...