<?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>Awakies &#187; Web Development</title>
	<atom:link href="http://blog.awakies.com/category/web-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.awakies.com</link>
	<description>Awakies is being in simple life sytle. Watch Movies, Listen Music, Take Photos, Learn Programming, touch in tech, Download free Software</description>
	<lastBuildDate>Wed, 24 Feb 2010 02:45:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Setting up your Local Server : Security considerations</title>
		<link>http://blog.awakies.com/2010/02/setting-up-your-local-server-security-considerations/</link>
		<comments>http://blog.awakies.com/2010/02/setting-up-your-local-server-security-considerations/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 02:45:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://blog.awakies.com/?p=111</guid>
		<description><![CDATA[Since testing is the primary goal here, I won&#8217;t discuss the security practices related to Windows+Apache+MySQL+PHP. But with a simple step you can secure your test server from external attacks: configure your firewall to block all Internet access to the server, as only your computer or your local network needs access to it.
On other hand, don&#8217;t think that test servers don’t need any protection. If you leave the server open to Internet, you&#8217;ll be exposed in the same way as production web sites, since hackers/crackers usually scans ranges of IP ...]]></description>
			<content:encoded><![CDATA[<p>Since testing is the primary goal here, I won&#8217;t discuss the security practices related to Windows+Apache+MySQL+PHP. But with a simple step you can secure your test server from external attacks: configure your firewall to block all Internet access to the server, as only your computer or your local network needs access to it.</p>
<p>On other hand, don&#8217;t think that test servers don’t need <em>any</em> protection. If you leave the server open to Internet, you&#8217;ll be exposed in the same way as production web sites, since hackers/crackers usually scans ranges of IP numbers looking for known vulnerabilities instead of targeting specific web sites.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.awakies.com/2010/02/setting-up-your-local-server-security-considerations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up your Local Server</title>
		<link>http://blog.awakies.com/2010/02/setting-up-your-local-server/</link>
		<comments>http://blog.awakies.com/2010/02/setting-up-your-local-server/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 02:44:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://blog.awakies.com/?p=109</guid>
		<description><![CDATA[When you are making a web page, the easiest way of view a page stored in your hard disk is double-clicking in the file, which usually results in the page being opened in your default browser. But this method it&#8217;s good enough for simple static pages, it&#8217;s not useful if you are using server side languages (PHP, Perl, ASP&#8230;), or even for pages that are static but use links relative to the server root (like &#8220;/index.html&#8221; or &#8220;/css/styles.css&#8221;). In this situations the solution is either upload the files to the ...]]></description>
			<content:encoded><![CDATA[<p>When you are making a web page, the easiest way of view a page stored in your hard disk is double-clicking in the file, which usually results in the page being opened in your default browser. But this method it&#8217;s good enough for simple static pages, it&#8217;s not useful if you are using server side languages (PHP, Perl, ASP&#8230;), or even for pages that are static but use links relative to the server root (like &#8220;/index.html&#8221; or &#8220;/css/styles.css&#8221;). In this situations the solution is either upload the files to the server of your web host or set up a test server in your local network/computer, which is the quick and safe way of testing your design changes. And you don’t need the internet connection for this.</p>
<p>Here I am trying to describe in a simple way how to set up an Apache server on Windows for testing purposes, with the option of include PHP and MySQL. This can be useful even if your web host runs on Linux/FreeBSD/Unix, since the functionality will be more or less the same, unless you use specific OS/server features. It can also be useful for learning and/or testing popular Apache modules like mod_rewrite that are not directly available for other servers like IIS.</p>
<p>Only PHP is covered since is free and widely used nowadays, where ASP is tied to IIS and Perl users probably prefer Linux. The same reasons apply to MySQL. I&#8217;m going to describe how to set up a standalone Apache server and then how to add PHP and MySQL, so people that don&#8217;t need PHP or MySQL can skip those steps.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.awakies.com/2010/02/setting-up-your-local-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
