Difference between revisions of "Site go live"

From GLMWiki
Jump to: navigation, search
Line 2: Line 2:
  
 
check that phing finalize has been run on checked out copy of the site and all prod directory js and css files have been updated.
 
check that phing finalize has been run on checked out copy of the site and all prod directory js and css files have been updated.
 +
 +
• move the client copy off into backup or webdev folder
 +
This should be done before you start moving the database to the production server
 +
move the dev52 copy out of the way
 +
 +
• run phing finalize to update all prod css and js files
 +
copy the current ~demo/build.xml file into the website directory and run 'phing finalize'
 +
 +
Note: Must have phing running on your machine
 +
 +
• update the discrption field in database so no devsys2 references are there
 +
Update the description field in the toolbox.pages table
 +
 +
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
 +
 +
• move the database to production servers
 +
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 http://cvs2.gaslightmedia.com/svn/dev/www.sitename.com \
 +
http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com
 +
 +
• check out 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
 +
 +
• update the .htaccess file
 +
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.

Revision as of 09:10, 21 September 2011

Check on reference to devsys2 in any application.

check that phing finalize has been run on checked out copy of the site and all prod directory js and css files have been updated.

• move the client copy off into backup or webdev folder This should be done before you start moving the database to the production server move the dev52 copy out of the way

• run phing finalize to update all prod css and js files copy the current ~demo/build.xml file into the website directory and run 'phing finalize'

Note: Must have phing running on your machine

• update the discrption field in database so no devsys2 references are there Update the description field in the toolbox.pages table

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

• move the database to production servers 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 http://cvs2.gaslightmedia.com/svn/dev/www.sitename.com \ http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com

• check out 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

• update the .htaccess file 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.