<?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:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Source Control &#8211; Part 3 &#8211; Installing a local Mercurial Server</title>
	<atom:link href="http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-a-local-mercurial-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-a-local-mercurial-server/</link>
	<description>an engineering approach to the software process</description>
	<lastBuildDate>Tue, 22 Feb 2011 03:12:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: eugeneduvenage</title>
		<link>http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-a-local-mercurial-server/comment-page-1/#comment-24</link>
		<dc:creator>eugeneduvenage</dc:creator>
		<pubDate>Thu, 12 Aug 2010 15:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-and-configuring-a-mercurial-server/#comment-24</guid>
		<description>Hi Harry, as far as I know for the example I gave where my hgwebdir_wsgi.py was located  at localhost/hg setting path_prefix=1 would be correct. If your repositories are not showing up I would check the following: 1) That you do indeed have initialised repositories (i.e. they have .hg files in the root of their directories. 2) That those directories are directly beneath the directory you specified in your hgweb.config. 3) That the security user that owns the app pool you are running your mercurial website under has read permissions on your repositories.

If you still can&#039;t get it working after checking these please send me a message via the contact form and I&#039;ll try help you out via email.</description>
		<content:encoded><![CDATA[<p>Hi Harry, as far as I know for the example I gave where my hgwebdir_wsgi.py was located  at localhost/hg setting path_prefix=1 would be correct. If your repositories are not showing up I would check the following: 1) That you do indeed have initialised repositories (i.e. they have .hg files in the root of their directories. 2) That those directories are directly beneath the directory you specified in your hgweb.config. 3) That the security user that owns the app pool you are running your mercurial website under has read permissions on your repositories.</p>
<p>If you still can&#8217;t get it working after checking these please send me a message via the contact form and I&#8217;ll try help you out via email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-a-local-mercurial-server/comment-page-1/#comment-23</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Thu, 12 Aug 2010 14:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.eugeneduvenage.com/2010/06/source-control-part-3-installing-and-configuring-a-mercurial-server/#comment-23</guid>
		<description>I have followed this tutorial and when I browse to the site I see the Mercurial Repositories page, but I cannot get any of the Repositories to show up.
Any ideas on what I missed or did wrong?

The only difference between mine and yours is that I set the path_prefix=0 as mentioned in Matt&#039;s post.

Any help would be appreciated.

Thanks!</description>
		<content:encoded><![CDATA[<p>I have followed this tutorial and when I browse to the site I see the Mercurial Repositories page, but I cannot get any of the Repositories to show up.<br />
Any ideas on what I missed or did wrong?</p>
<p>The only difference between mine and yours is that I set the path_prefix=0 as mentioned in Matt&#8217;s post.</p>
<p>Any help would be appreciated.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

