Site go live

• Move the client copy into webdev directory

This should be done before you start moving the database to the production server
move the dev52 copy out of the way

• Check on email addresses to make sure they're set
• Make sure meta description and title in template
• Remove the index.html file also from version control
• Update the description field in the toolbox.pages table

set search_path to toolbox;
begin work;
update paragraphs set description = replace(description, 'dev52.gaslightmedia.com/', );
commit work;

• Update the url field in the rotating images table so the url reference is not dev52

set search_path to rotatingimages;
begin work;
update rotating_images set url = replace(url, 'dev52.gaslightmedia.com/', );
commit work;

• Make sure the database used matches the one in the config/server.ini now using ds4 not ds3
• Move the database to production server

when you do a dump you may have to use full column insert and not a tar file 
as grabbing database from ds3 from a different psql version
If you go from the same version you can use the -Fc for a compressed file dump which will be much faster to reload 
a huge database copy.

• Move svn copy into prod

svn mv [url] [url]
example:
svn mv -m "move to production" http://cvs2.gaslightmedia.com/svn/dev/www.sitename.com \
http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com

• Check out the site to production server

When you checkout the site to the live server first check it out as a different folder name
svn co http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com new.sitename.com
then move in the needed folders like admin/logs and move the original out of the way to hte backup
directory and  move in your new copy.

• Verify that the GLM_site_check.phtml file exists on production checkout

Verify not only that it exists but is setup to pull in the setup.phtml file and get the correct database connection.
New sites should be using version 2.0 of this file
Also check that the file has correct db host name (ds4)