+TESTING
+
+Use -dryrun as a parameter to test the copy. This does everything
+and then rolls back the database at the end.
+
+STAGING SERVER
+
+It is possible to use this script to implement a staging server.
+
+The basic setup is that you have two hosts (called for example
+'staging.example.com' and 'www.example.com' where the latter
+is the live site). Create the staging host first (or use
+copy_host to duplicate it from the live host if you already
+have one). Do all editing on the staging server.
+
+When you are satisfied with the state of the staging server
+and are ready to go live, use the following command:
+
+ copy_host -shost staging.example.com -dhost www.example.com,example.com \
+ -overwrite -disableedit -enableviewanon
+
+The key options to take note of are:
+
+ -overwrite If the dhost already exists, it can be overwritten.
+ (In fact what happens is that the existing destination
+ host is renamed to a unique name like 'deleted-<timestamp>')
+
+ -disableedit This disables the editing capability of all users on
+ the destination host. This stops users from accidentally
+ editing the live site.
+
+ -enableviewanon This enables anonymous viewing on the destination
+ host (assuming that the staging server is configured to
+ only allow logged in users to view, which is usually the
+ right thing to do).
+