<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Best practices in deploying and optimizing your Plone site</title>
	<atom:link href="http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/</link>
	<description>Python, Django and Plone web application development</description>
	<lastBuildDate>Tue, 24 Jan 2012 21:50:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Avoiding buildout failure when pypi is down using collective.eggproxy &#124; Jazkarta Blog</title>
		<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/#comment-26</link>
		<dc:creator><![CDATA[Avoiding buildout failure when pypi is down using collective.eggproxy &#124; Jazkarta Blog]]></dc:creator>
		<pubDate>Tue, 01 Sep 2009 23:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jazkarta.com/?p=130#comment-26</guid>
		<description><![CDATA[[...] my last post in the continuing series about deploying and optimizing Plone sites, we learned how to make a [...]]]></description>
		<content:encoded><![CDATA[<p>[...] my last post in the continuing series about deploying and optimizing Plone sites, we learned how to make a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate</title>
		<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/#comment-25</link>
		<dc:creator><![CDATA[nate]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 14:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jazkarta.com/?p=130#comment-25</guid>
		<description><![CDATA[Yeah, it looks like the only difference is that the /thirdparty has python_ldap and PILwoTk, whereas the /release/3.3 just has PIL-1.1.6 and no python_ldap. So if you need python_ldap or PILwoTk, then you should use /thirdparty, otherwise /release/3.3 should work fine.]]></description>
		<content:encoded><![CDATA[<p>Yeah, it looks like the only difference is that the /thirdparty has python_ldap and PILwoTk, whereas the /release/3.3 just has PIL-1.1.6 and no python_ldap. So if you need python_ldap or PILwoTk, then you should use /thirdparty, otherwise /release/3.3 should work fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate</title>
		<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/#comment-24</link>
		<dc:creator><![CDATA[nate]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 14:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jazkarta.com/?p=130#comment-24</guid>
		<description><![CDATA[Geir - I am not proposing that one should use easy_install to install Plone. The article shows using buildout to install Plone. I only mention easy_install because it&#039;s an easy way to get virtualenv installed, which *does* work with buildout. In subsequent articles we will be using easy_install to install other tools such as collective.releaser, collective.dist and ZopeSkel.]]></description>
		<content:encoded><![CDATA[<p>Geir &#8211; I am not proposing that one should use easy_install to install Plone. The article shows using buildout to install Plone. I only mention easy_install because it&#8217;s an easy way to get virtualenv installed, which *does* work with buildout. In subsequent articles we will be using easy_install to install other tools such as collective.releaser, collective.dist and ZopeSkel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geir Bækholt</title>
		<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/#comment-23</link>
		<dc:creator><![CDATA[Geir Bækholt]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 13:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jazkarta.com/?p=130#comment-23</guid>
		<description><![CDATA[Is &quot;best practices&quot; really using easy_install and virtualenv?

As far as i am aware  — this is completely broken — and the only recommended way of installing Plone is via buildout or the universal installer...

I was convinced that easy_install for Plone had big red letters of warning saying &quot;DON&#039;T USE&quot; all over it.

Just use buildout.]]></description>
		<content:encoded><![CDATA[<p>Is &#8220;best practices&#8221; really using easy_install and virtualenv?</p>
<p>As far as i am aware  — this is completely broken — and the only recommended way of installing Plone is via buildout or the universal installer&#8230;</p>
<p>I was convinced that easy_install for Plone had big red letters of warning saying &#8220;DON&#8217;T USE&#8221; all over it.</p>
<p>Just use buildout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Jacobs</title>
		<link>http://blog.jazkarta.com/2009/08/25/best-practices-in-deploying-and-optimizing-your-plone-site/#comment-22</link>
		<dc:creator><![CDATA[Peter Jacobs]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 10:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jazkarta.com/?p=130#comment-22</guid>
		<description><![CDATA[Thank you, I have looked at my buildout script and removed the PILwoTk recipe, it works fine like you show here.

You use:
 find-links = http://dist.plone.org/thirdparty
but this also works for me (probably not much different?):
 find-links = http://dist.plone.org/release/3.3/]]></description>
		<content:encoded><![CDATA[<p>Thank you, I have looked at my buildout script and removed the PILwoTk recipe, it works fine like you show here.</p>
<p>You use:<br />
 find-links = <a href="http://dist.plone.org/thirdparty" rel="nofollow">http://dist.plone.org/thirdparty</a><br />
but this also works for me (probably not much different?):<br />
 find-links = <a href="http://dist.plone.org/release/3.3/" rel="nofollow">http://dist.plone.org/release/3.3/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

