<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.6.5" -->
<rss version="0.92">
<channel>
	<title>Project Deploy* Developer Blog</title>
	<link>http://projectdeploy.org/blog</link>
	<description></description>
	<lastBuildDate>Fri, 20 Feb 2009 10:53:35 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Release of Deploy 1.4 RC1</title>
		<description><![CDATA[Today I am releasing the first release candidate for Deploy* 1.4. It has a ton more features and the internals are much, much different.
For a list of all the current changes: http://projectdeploy.org/beta/docs/CHANGE_LOG.txt
For a list for the roadmap (I&#8217;m working on making this a little nicer): http://projectdeploy.org/beta/docs/ROADMAP.txt
You can get to the beta by going to http://projectdeploy.org/beta
I&#8217;m [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/release-of-deploy-14-rc1/</link>
			</item>
	<item>
		<title>Deploy* 1.4 Upcoming Feature List</title>
		<description><![CDATA[When you don&#8217;t hear much from a developer it&#8217;s usually because he is hard at work at programming. At this time not everything is finished and tested, but here are some for sure upcoming features for 1.4:

2 new built in functions that make it easier for non programmers to add and create files

create_empty_file() creates an [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/deploy-14-upcoming-feature-list/</link>
			</item>
	<item>
		<title>How Deploy* Works</title>
		<description><![CDATA[Even if you are not a programmer you might wonder how exactly does Deploy* work? Does it just copy files over? Does it create them on the fly? Is it magic?
As of 1.3.2 and under Deploy* goes through a few processes before making that final zip you get at the end after you push that [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/how-deploy-works/</link>
			</item>
	<item>
		<title>Why Would I Use Deploy*?</title>
		<description><![CDATA[The people who don&#8217;t like Deploy* usually have one comment, &#8220;Why would I use Deploy*? What it does is pretty trivial. I can just make a directory and copy it.&#8221; My response is always about the same and it&#8217;s basically, &#8220;Yes, you can.&#8221;
Now with that in mind, why would you use Deploy*? For me it&#8217;s [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/why-would-i-use-deploy/</link>
			</item>
	<item>
		<title>The Road to Deploy* 2.0</title>
		<description><![CDATA[The Road to Deploy* 2.0 seems far away from now, but I want to share some ideas I have for 2.0. I will not share all of the ideas because it would take the fun off the 2.0 release.
The main request I get is &#8220;can you include X file&#8221;. Yes, I could keep adding file [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/the-road-to-deploy-2/</link>
			</item>
	<item>
		<title>Version 1.3.2</title>
		<description><![CDATA[Fixes a validation error for HTML 4.01 Strict and HTML 4.01 Transitional users by removing a slash at the end of self closed tags.
If something isn&#8217;t working correctly let me know at projectdeploy.org/help. I tried doing as many possible combinations and it seems to be working fine, but I might have missed a certain combo.
]]></description>
		<link>http://projectdeploy.org/blog/posts/version-1_3_2/</link>
			</item>
	<item>
		<title>Version 1.3.1</title>
		<description><![CDATA[This fixes the &#8220;Permissions Error&#8221; and adds some functionality to the Fluid side of things:

Deploy* would display an error if the root folder was not set writeable, or 755, but Deploy* will take care of permissions now for both the root and deploys folder.
Deploy* will now catch the &#8220;Permissions Error&#8221; and highlight in bright yellow [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/version-1_3_1/</link>
			</item>
	<item>
		<title>The &#8220;Permission Denied&#8221; Error</title>
		<description><![CDATA[It will now (version 1.3.1) change the permissions automatically with the chmod() function.
One user (possibly more?) had an issue installing this, which is my fault for not providing better documentation on how Deploy* works (I have added an install.txt file in Deploy* 1.3.1), however, that is another post. The error will read something like:
warning: mkdir() [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/the-permission-denied-error/</link>
			</item>
	<item>
		<title>Why the name Deploy*?</title>
		<description><![CDATA[Another question I get frequently is, why the name Deploy*. When I was thinking of a name, deploy was the perfect word.
The New Oxford Dictionary says deploy(verb) means: &#8220;bring into effective action; utilize&#8221;.
Deploy* trys to bring your web project into effective action and ready to be utilized to create the project right away without the [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/why-the-name-deploy/</link>
			</item>
	<item>
		<title>Is It Project Deploy* or just Deploy*</title>
		<description><![CDATA[Short answer, it&#8217;s both.
Long answer, Project Deploy* is the web site that hosts Deploy*. The reason the site has the logo &#8220;deploy*&#8221; on this web site and blog is because Deploy* is the web application that runs on projectdeploy.org. When you download Deploy* you are downloading Deploy* from the project&#8217;s home, projectdeploy.org.
I know a few [...]]]></description>
		<link>http://projectdeploy.org/blog/posts/project-deploy-or-deploy/</link>
			</item>
</channel>
</rss>
