<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Server Hacks Blog - Hacks for Dedicated/VPS Servers, SSH, and Plesk &#187; upgrade</title>
	<atom:link href="http://webserverhacks.com/tag/upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://webserverhacks.com</link>
	<description>Hacks for Dedicated/VPS Servers, SSH, and Plesk</description>
	<lastBuildDate>Tue, 01 Nov 2011 23:56:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>WordPress Hack – How to Upgrade WordPress in 15 seconds using SSH/Wget!</title>
		<link>http://webserverhacks.com/wordpress-hacks/wordpress-hack-%e2%80%93-how-to-upgrade-wordpress-in-15-seconds-using-sshwget/</link>
		<comments>http://webserverhacks.com/wordpress-hacks/wordpress-hack-%e2%80%93-how-to-upgrade-wordpress-in-15-seconds-using-sshwget/#comments</comments>
		<pubDate>Mon, 04 Apr 2011 00:55:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress Hacks]]></category>
		<category><![CDATA[15 seconds]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wget]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wordpress hack]]></category>

		<guid isPermaLink="false">http://webserverhacks.com/?p=83</guid>
		<description><![CDATA[I&#8217;ve been upgrading WordPress for almost 4 years now and since I manage about 20 blogs, I have learned to figure out how to upgrade your WordPress faster than ever using SSH and wget command. For one, you will need a dedicated server/VPS that supports SSH. Otherwise you won&#8217;t be able to do it. Here&#8217;s exactly how I do it. 1) I go to my WordPress directory using the command cd. ~ 2 seconds 2) I use wget to pull the latest wordpress files, &#8220;wget http://wordpress.org/latest.tar.gz&#8221; ~ 3 seconds 3) Then I unzip the tar file using &#8220;tar xvf latest.tar.gz&#8221; ~ 5 seconds (see tar command howto here) 4) Then I remove the wp-admin and wp-includes directories by doing &#8220;rm wp-admin -rf&#8221; and &#8220;rm wp-includes -rf&#8220;. ~ 3 seconds 5) Next I will copy over the old WordPress files with the new ones using commands, &#8220;cp wordress/* . -rf &#8211;reply=yes&#8221; ~ 2 seconds. 6) I am done, that&#8217;s 2+3+5+3+2=15 seconds. If you are on at least a quad-core CPU server, downloading and unzipping should be rather fast but for those of you on slower servers, give it couple more seconds as download/unzip will take longer. This is lightening fast compared &#8230; <a href="http://webserverhacks.com/wordpress-hacks/wordpress-hack-%e2%80%93-how-to-upgrade-wordpress-in-15-seconds-using-sshwget/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been upgrading WordPress for almost 4 years now and since I manage about 20 blogs, I have learned to figure out how to upgrade your WordPress faster than ever using SSH and wget command.</p>
<p>For one, you will need a dedicated server/VPS that supports SSH.  Otherwise you won&#8217;t be able to do it.</p>
<p>Here&#8217;s exactly how I do it.</p>
<p>1) I go to my WordPress directory using the command <a target="_blank" href="http://www.computerhope.com/unix/ucd.htm" >cd</a>. ~ 2 seconds</p>
<p>2) I use <a target="_blank" href="http://linux.about.com/od/commands/l/blcmdl1_wget.htm" >wget</a> to pull the latest wordpress files, &#8220;<strong>wget http://wordpress.org/latest.tar.gz</strong>&#8221; ~ 3 seconds</p>
<p>3) Then I unzip the tar file using &#8220;<strong>tar xvf latest.tar.gz</strong>&#8221; ~ 5 seconds (<a target="_blank" href="http://www.computerhope.com/unix/utar.htm" >see tar command howto here</a>)</p>
<p>4) Then I remove the wp-admin and wp-includes directories by doing &#8220;<strong>rm wp-admin -rf</strong>&#8221; and &#8220;<strong>rm wp-includes -rf</strong>&#8220;. ~ 3 seconds</p>
<p>5) Next I will copy over the old WordPress files with the new ones using commands, &#8220;<strong>cp wordress/* . -rf &#8211;reply=yes</strong>&#8221; ~ 2 seconds.</p>
<p>6) I am done, that&#8217;s 2+3+5+3+2=15 seconds.  If you are on at least a quad-core CPU server, downloading and unzipping should be rather fast but for those of you on slower servers, give it couple more seconds as download/unzip will take longer.</p>
<p>This is lightening fast compared to downloading WordPress files to your computer, unzipping it then uploading them to your website via FTP.  And if you are on shared hosting, sometimes uploading FTP can take forever.</p>
<p>Even if you use built-in upgrade functions in WordPress, you are not going to beat SSH, not even a chance.</p>
<p>Of course, even better than this is to write a simple bash shell script that will do all the above for you.  Then you could probably do it in just about 5 seconds.  I will try to write a script soon and let you know on that btw.  (I just realize it!)</p>
]]></content:encoded>
			<wfw:commentRss>http://webserverhacks.com/wordpress-hacks/wordpress-hack-%e2%80%93-how-to-upgrade-wordpress-in-15-seconds-using-sshwget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CentOS Hack – How to Upgrade from PHP 5.1.6 to 5.2!</title>
		<link>http://webserverhacks.com/web-server-hacks/centos-hack-%e2%80%93-how-to-upgrade-from-php-5-1-6-to-5-2/</link>
		<comments>http://webserverhacks.com/web-server-hacks/centos-hack-%e2%80%93-how-to-upgrade-from-php-5-1-6-to-5-2/#comments</comments>
		<pubDate>Mon, 04 Apr 2011 00:54:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Server Hacks]]></category>
		<category><![CDATA[5.2]]></category>
		<category><![CDATA[centos hack]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[php 5.1.6]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://webserverhacks.com/?p=81</guid>
		<description><![CDATA[For those of you who are trying to upgrade from PHP 5.2 because your application requires PHP 5.2 or above, you can use this hack to upgrade your web server running CentOS. Since CentOS doesn&#8217;t officially support PHP 5.2 officially yet, this could possibly be a great workaround. Word of caution, this hack has worked fine for me for a new Twitter app site I am making that requires use of PHP 5.2 but if you have non-standard customizations to your server, you might want to test it first. I&#8217;ve also found that JSON library that comes with PHP 5.2 is like 20 times faster rather than trying to run separate JSON libraries with PHP 5.1.6. It made a HUGE difference let me just say in page loading times. (Like .90 seconds versus 0.003 seconds.) This guide describes how to upgrade the standard PHP 5.1.x packages in CentOS 5.x 32-bit to the current development versions 5.2.x. These instructions were created using CentOS 5.3 32-bit and with the following PHP packages installed: # rpm -qa &#124;grep php php-common-5.1.6-15.el5.i386 php-cli-5.1.6-15.el5.i386 php-5.1.6-15.el5.i386 php-pdo-5.1.6-15.el5.i386 php-bcmath-5.1.6-15.el5.i386 php-ldap-5.1.6-15.el5.i386 php-devel-5.1.6-15.el5.i386 php-gd-5.1.6-15.el5.i386 php-xml-5.1.6-15.el5.i386 php-mbstring-5.1.6-15.el5.i386 php-mysql-5.1.6-15.el5.i386 php-dba-5.1.6-15.el5.i386 As long as you&#8217;re using the standard PHP packages on your CentOS &#8230; <a href="http://webserverhacks.com/web-server-hacks/centos-hack-%e2%80%93-how-to-upgrade-from-php-5-1-6-to-5-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>For those of you who are trying to upgrade from PHP 5.2 because your application requires PHP 5.2 or above, you can use this hack to upgrade your web server running CentOS.  Since CentOS doesn&#8217;t officially support PHP 5.2 officially yet, this could possibly be a great workaround.</p>
<p>Word of caution, this hack has worked fine for me for a new Twitter app site I am making that requires use of PHP 5.2 but if you have non-standard customizations to your server, you might want to test it first.</p>
<p>I&#8217;ve also found that JSON library that comes with PHP 5.2 is like 20 times faster rather than trying to run separate JSON libraries with PHP 5.1.6.  It made a HUGE difference let me just say in page loading times. (Like .90 seconds versus 0.003 seconds.)</p>
<blockquote><p>This guide describes how to upgrade the standard PHP 5.1.x packages in CentOS 5.x 32-bit to the current development versions 5.2.x. These instructions were created using CentOS 5.3 32-bit and with the following PHP packages installed:</p>
<p># rpm -qa |grep php</p>
<p>php-common-5.1.6-15.el5.i386<br /> <br />
php-cli-5.1.6-15.el5.i386<br /> <br />
php-5.1.6-15.el5.i386<br /> <br />
php-pdo-5.1.6-15.el5.i386<br /> <br />
php-bcmath-5.1.6-15.el5.i386<br /> <br />
php-ldap-5.1.6-15.el5.i386<br /> <br />
php-devel-5.1.6-15.el5.i386<br /> <br />
php-gd-5.1.6-15.el5.i386<br /> <br />
php-xml-5.1.6-15.el5.i386<br /> <br />
php-mbstring-5.1.6-15.el5.i386<br /> <br />
php-mysql-5.1.6-15.el5.i386<br /> <br />
php-dba-5.1.6-15.el5.i386</p>
<p>As long as you&#8217;re using the standard PHP packages on your CentOS server you won&#8217;t need to do anything extra. If you&#8217;re using extra PHP packages that aren&#8217;t part of the standard CentOS repositories (like php-mcrypt) you&#8217;ll have to remove them or find updated versions of them.</p></blockquote>
<p><a target="_blank" href="http://wiki.centos.org/HowTos/PHP_5.1_To_5.2" >via cent.os</a> </p>
]]></content:encoded>
			<wfw:commentRss>http://webserverhacks.com/web-server-hacks/centos-hack-%e2%80%93-how-to-upgrade-from-php-5-1-6-to-5-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

