Difference between revisions of "Site go live"

From GLMWiki
Jump to: navigation, search
Line 1: Line 1:
−
Check on reference to devsys2 in any application.
+
*Move the client copy into webdev directory
−
 
+
This should be done before you start moving the database to the production server
−
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 dev52 copy out of the way
−
 
+
*Check on email addresses to make sure they're set
−
• move the client copy off into backup or webdev folder
+
*Make sure meta description and title in template
−
This should be done before you start moving the database to the production server
+
*Remove the index.html file also from version control
−
move the dev52 copy out of the way
+
*Update the description field in the toolbox.pages table
−
 
+
set search_path to toolbox;
−
• run phing finalize to update all prod css and js files
+
begin work;
−
copy the current ~demo/build.xml file into the website directory and run 'phing finalize'
+
update paragraphs set description = replace(description, 'dev52.gaslightmedia.com/', '');
−
 
+
commit work;
−
Note: Must have phing running on your machine
+
*Update the url field in the rotating images table so the url reference is not dev52
−
 
+
set search_path to rotatingimages;
−
• update the discrption field in database so no devsys2 references are there
+
begin work;
−
Update the description field in the toolbox.pages table
+
update rotating_images set url = replace(url, 'dev52.gaslightmedia.com/', '');
−
 
+
commit work;
−
begin work;
+
*Make sure the database used matches the one in the config/server.ini now using ds4 not ds3
−
update paragraphs set description = replace(description, 'dev52.gaslightmedia.com/', '');
+
*Move the database to production server
−
commit work;
+
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
−
Update the url field in the rotating images table so the url reference is not dev52
+
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 the database to production servers
+
*Move svn copy into prod
−
when you do a dump you may have to use full column insert and not a tar file  
+
svn mv [url] [url]
−
as grabbing database from ds3 from a different psql version
+
example:
−
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.
+
svn mv -m "move to production" http://cvs2.gaslightmedia.com/svn/dev/www.sitename.com \
−
 
+
http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com
−
• move svn copy into prod
+
*Check out the site to production server
−
svn mv [url] [url]
+
When you checkout the site to the live server first check it out as a different folder name
−
example:
+
svn co http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com new.sitename.com
−
svn mv http://cvs2.gaslightmedia.com/svn/dev/www.sitename.com \
+
then move in the needed folders like admin/logs and move the original out of the way to hte backup
−
http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com
+
directory and move in your new copy.
−
 
+
*Verify that the GLM_site_check.phtml file exists on production checkout
−
• check out site to production server
+
Verify not only that it exists but is setup to pull in the setup.phtml file and get the correct database connection.
−
When you checkout the site to the live server first check it out as a different folder name
+
New sites should be using version 2.0 of this file
−
svn co http://cvs2.gaslightmedia.com/svn/prod/www.sitename.com new.sitename.com
+
Also check that the file has correct db host name (ds4)
−
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 12:50, 25 May 2012

  • 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)
Retrieved from "https://wiki.gaslightmedia.com/index.php?title=Site_go_live&oldid=753"