<?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/"
		>
<channel>
	<title>Comments on: About</title>
	<atom:link href="http://colin.mollenhour.com/about/feed/" rel="self" type="application/rss+xml" />
	<link>http://colin.mollenhour.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 30 Dec 2011 22:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-96</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Sun, 02 Oct 2011 02:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-96</guid>
		<description>Hi Justin. If you don&#039;t want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:&lt;br&gt;&lt;br&gt;@shell &lt;br&gt;cd $PROJECT; &lt;br&gt;mkdir -f .installed &lt;br&gt;for ext in `cat $MODULE/extensions.txt`; do &lt;br&gt;if [ ! -f .installed/$ext ]; then&lt;br&gt;./pear install $ext &amp;&amp; touch .installed/$ext; &lt;br&gt;fi &lt;br&gt;done</description>
		<content:encoded><![CDATA[<p>Hi Justin. If you don&#39;t want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:</p>
<p>@shell <br />cd $PROJECT; <br />mkdir -f .installed <br />for ext in `cat $MODULE/extensions.txt`; do <br />if [ ! -f .installed/$ext ]; then<br />./pear install $ext &amp;&amp; touch .installed/$ext; <br />fi <br />done</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-97</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Sun, 02 Oct 2011 02:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-97</guid>
		<description>Hi Justin. If you don&#039;t want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:&lt;br&gt;&lt;br&gt;@shell &lt;br&gt;cd $PROJECT; &lt;br&gt;mkdir -f .installed &lt;br&gt;for ext in `cat $MODULE/extensions.txt`; do &lt;br&gt;if [ ! -f .installed/$ext ]; then&lt;br&gt;./pear install $ext &amp;&amp; touch .installed/$ext; &lt;br&gt;fi &lt;br&gt;done</description>
		<content:encoded><![CDATA[<p>Hi Justin. If you don&#39;t want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:</p>
<p>@shell <br />cd $PROJECT; <br />mkdir -f .installed <br />for ext in `cat $MODULE/extensions.txt`; do <br />if [ ! -f .installed/$ext ]; then<br />./pear install $ext &amp;&amp; touch .installed/$ext; <br />fi <br />done</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-95</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sun, 02 Oct 2011 01:55:49 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-95</guid>
		<description>Hi Collin, I&#039;m looking forward to using Modman, which seems like a great utility.  I just have a question about best practices when it comes to 3rd party Magento extensions.  This must be a simple or obvious question as I haven&#039;t been able to find anyone addressing it online, but in a nutshell:  is there a best practice for dealing with 3rd party extensions when developing a Magento store, using source control and modman?  I&#039;d rather not check 3rd party extensions in, so are they something that wouldn&#039;t even typically be handled by modman?  Just install the extensions I want by hand in my production, staging and dev environments individually?  Thanks for any thoughts you may have</description>
		<content:encoded><![CDATA[<p>Hi Collin, I&#39;m looking forward to using Modman, which seems like a great utility.  I just have a question about best practices when it comes to 3rd party Magento extensions.  This must be a simple or obvious question as I haven&#39;t been able to find anyone addressing it online, but in a nutshell:  is there a best practice for dealing with 3rd party extensions when developing a Magento store, using source control and modman?  I&#39;d rather not check 3rd party extensions in, so are they something that wouldn&#39;t even typically be handled by modman?  Just install the extensions I want by hand in my production, staging and dev environments individually?  Thanks for any thoughts you may have</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-93</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Mon, 12 Sep 2011 07:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-93</guid>
		<description>&lt;br&gt;&lt;br&gt;&lt;meta content=&quot;text/html; charset=UTF-8&quot; http-equiv=&quot;Content-Type&quot;&gt; &lt;br&gt;&lt;br&gt;Maybe your comment didn&#039;t come through as expected, but I think&lt;br&gt;you&#039;re asking about configuring a prefix to avoid keyspace collisions?&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I&lt;br&gt;would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control&lt;br&gt;the amount of memory each installation can use.&lt;br&gt;&lt;br&gt;&lt;br&gt;</description>
		<content:encoded><![CDATA[<p>&lt;meta content=&#8221;text/html; charset=UTF-8&#8243; http-equiv=&#8221;Content-Type&#8221;&gt; </p>
<p>Maybe your comment didn&#39;t come through as expected, but I think<br />you&#39;re asking about configuring a prefix to avoid keyspace collisions?</p>
<p>The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I<br />would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control<br />the amount of memory each installation can use.</p>
<p></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-94</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Mon, 12 Sep 2011 07:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-94</guid>
		<description>&lt;br&gt;&lt;br&gt;&lt;meta content=&quot;text/html; charset=UTF-8&quot; http-equiv=&quot;Content-Type&quot;&gt; &lt;br&gt;&lt;br&gt;Maybe your comment didn&#039;t come through as expected, but I think&lt;br&gt;you&#039;re asking about configuring a prefix to avoid keyspace collisions?&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I&lt;br&gt;would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control&lt;br&gt;the amount of memory each installation can use.&lt;br&gt;&lt;br&gt;&lt;br&gt;</description>
		<content:encoded><![CDATA[<p>&lt;meta content=&#8221;text/html; charset=UTF-8&#8243; http-equiv=&#8221;Content-Type&#8221;&gt; </p>
<p>Maybe your comment didn&#39;t come through as expected, but I think<br />you&#39;re asking about configuring a prefix to avoid keyspace collisions?</p>
<p>The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I<br />would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control<br />the amount of memory each installation can use.</p>
<p></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-92</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 12 Sep 2011 03:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-92</guid>
		<description>Hi Collin,&lt;br&gt;I have a quick question about Magento config for Zend_Cache_Backend_Redis.&lt;br&gt;For APC cache, in case of multiple websites/per server you need to use &#039;&lt;prefix&gt;..&lt;/prefix&gt;&#039; . Do you need to do anything like that if you are using Zend_Cache_Backend_Redis ?&lt;br&gt;Thank you!</description>
		<content:encoded><![CDATA[<p>Hi Collin,<br />I have a quick question about Magento config for Zend_Cache_Backend_Redis.<br />For APC cache, in case of multiple websites/per server you need to use &#39;&lt;prefix&gt;..&lt;/prefix&gt;&#39; . Do you need to do anything like that if you are using Zend_Cache_Backend_Redis ?<br />Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-91</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Sat, 27 Aug 2011 07:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-91</guid>
		<description>Yep: @colinmollenhour</description>
		<content:encoded><![CDATA[<p>Yep: @colinmollenhour</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinai</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-90</link>
		<dc:creator>Vinai</dc:creator>
		<pubDate>Sat, 27 Aug 2011 02:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-90</guid>
		<description>Hi Collin, do you twitter?</description>
		<content:encoded><![CDATA[<p>Hi Collin, do you twitter?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Hållén</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-88</link>
		<dc:creator>Stefan Hållén</dc:creator>
		<pubDate>Sun, 29 May 2011 21:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-88</guid>
		<description>So this is probably totally the wrong place to ask this question, but how would one go about to execute a query like:&lt;br&gt;{ $or  : [ { start : { $gt : 100}, start : { $lt : 200} }, { end : { $gt : 100}, end : { $lt : 200} } ] }&lt;br&gt;In the mongodb odm wrapper? :)</description>
		<content:encoded><![CDATA[<p>So this is probably totally the wrong place to ask this question, but how would one go about to execute a query like:<br />{ $or  : [ { start : { $gt : 100}, start : { $lt : 200} }, { end : { $gt : 100}, end : { $lt : 200} } ] }<br />In the mongodb odm wrapper? :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Mollenhour</title>
		<link>http://colin.mollenhour.com/about/comment-page-1/#comment-85</link>
		<dc:creator>Colin Mollenhour</dc:creator>
		<pubDate>Thu, 14 Apr 2011 01:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/wordpress/?page_id=2#comment-85</guid>
		<description>The problems that come along with using hardlinks are that detecting and repairing situations where files were moved/renamed/deleted becomes very difficult. Also to uninstall a module becomes potentially much more problematic. I.e. with symlinks I can remove a module by deleting it and running modman repair (thanks to the easy detection of broken symlinks). Also other problems such as having the root of your site as a repository would cause weird repository conflicts, etc..</description>
		<content:encoded><![CDATA[<p>The problems that come along with using hardlinks are that detecting and repairing situations where files were moved/renamed/deleted becomes very difficult. Also to uninstall a module becomes potentially much more problematic. I.e. with symlinks I can remove a module by deleting it and running modman repair (thanks to the easy detection of broken symlinks). Also other problems such as having the root of your site as a repository would cause weird repository conflicts, etc..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

