Difference between revisions of "Site go live"

Revision as of 09:35, 20 December 2013

• 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, client files, Phing folder file also from version control.
• Ensure that search is enabled. Task Chuck with indexing as soon as the site is live.
• Ensure Google Analytics Tracking code is migrated.
• Ensure that all calls to the mobile template are removed.
• Ensure that Event Management data is migrated.
• Ensure that debug code is removed. In particular: Remove the "dimensions" id div near the top of the template. Grep for "console.log" and remove or at least comment all instances.
• Update the description field in the toolbox.pages table

----------
for dev52
----------
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;
----------
for dev53
----------
set search_path to toolbox;
begin work;
update paragraphs set description = replace(description, 'dev53.gaslightmedia.com/', '');
commit work;

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

 set search_path to rotatingimages;
 begin work;
 update rotating_images set url = replace(url, 'dev53.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.

pg_dump -Fc -h devdb -f {dbName}.tar {dbName}

createdb -h ds4 {dbName}
pg_restore -d {dbName} -h ds4 {dbName}.tar

• 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)

• CKEditor folders must be present

These folders need to be there
CKImages/
  editedImages 
PHPImageEditor/
  editimagesoriginal
  editimagespng
  editimagesworkwith

• For new member database empty the exposure reporting table of test data
• Update .htaccess file on server and commit

update the .htaccess after you move in the site comment out the baseurl part
if the site has gone live already (not ip) then you can update and uncomment the two lines that will keep people  
from using no www. in front of the url.

• Move the old database (if there was one) so no connections are made to old data
• Once live empty the cache directory and update .htaccess file for redirect if nothing before domain name (no www)
• If the flexy option forceCompile is turned off you'll have to set it to on then run the site at the url to get rid of any ip address in the flexy templates. then remember to turn it back off.

For member databases check that there's no dev53 or dev52 references in the members.member table. they may stick in those as links. also member files are still stored in files so you'll have to upload them to the live server.