<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Docunext Mirrors</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/" />
    <link rel="self" type="application/atom+xml" href="http://www.mirrors.docunext.com/blog/atom.xml" />
    <id>tag:www.mirrors.docunext.com,2008-09-16:/blog//185</id>
    <updated>2010-03-06T08:36:14Z</updated>
    <subtitle>Git and Subversion mirrors of my favorite projects.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>

<entry>
    <title>Raw Source Code</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2009/10/raw-source-code.html" />
    <id>tag:www.mirrors.docunext.com,2009:/blog//185.16893</id>

    <published>2009-10-25T00:13:36Z</published>
    <updated>2010-03-06T08:36:14Z</updated>

    <summary>There are many projects that only provide their open source licensed code in as a single archive download. For instance: mathopd and ftpproxy. In these cases, I&apos;ve actually had a bit of a tough time trying to decide how to...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    <category term="highlight" label="highlight" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="source" label="source" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="syntax" label="syntax" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[<p>There are many projects that only provide their open source licensed code in as a single archive download. For instance: mathopd and ftpproxy.</p>

<p>In these cases, I've actually had a bit of a tough time trying to decide how to display the code on these mirrors.</p>

<p>The past couple of days I've tried some source highlighting software out: </p>

<ul>
<li>source-highlight</li>
<li>highlight</li>
</ul>

<p>I've also come up with some shell scripts to automate the process. I still have a couple of questions to answer, but I think I'll figure those out momentarily and get publishing more code very soon. Here's to open source!</p>

<p>NOTE: I've removed the examples I had here. </p>
]]>
        

    </content>
</entry>

<entry>
    <title>Better Mirrors Performance</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2009/06/better-mirrors-performance.html" />
    <id>tag:www.mirrors.docunext.com,2009:/blog//185.3863</id>

    <published>2009-06-23T13:14:11Z</published>
    <updated>2009-06-23T13:15:32Z</updated>

    <summary>I&apos;m pleased to report that the Docunext Mirrors are working better than ever. Cgit is working out great, and I&apos;ve hacked up WebSVN to work much better. I&apos;ve also set Varnish to cache the pages properly, so that should help...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
        <category term="Docunext Mirrors" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        I&apos;m pleased to report that the Docunext Mirrors are working better than ever. Cgit is working out great, and I&apos;ve hacked up WebSVN to work much better. I&apos;ve also set Varnish to cache the pages properly, so that should help too. :-)
        
    </content>
</entry>

<entry>
    <title>SVN::Web is All Good, For Now</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2009/04/all-good-for-now.html" />
    <id>tag:www.mirrors.docunext.com,2009:/blog//184.1479</id>

    <published>2009-04-15T00:33:13Z</published>
    <updated>2009-04-15T05:33:26Z</updated>

    <summary>The Subversion issues took awhile to fix, but for now things are OK enough with SVN::Web.Other news: we&apos;re now using cgit for git repositories. Its fast and light, no official FastCGI support yet, but I hacked it into place during...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
        <category term="Docunext Mirrors" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[The Subversion issues took awhile to fix, but for now things are OK enough with SVN::Web.<br /><br />Other news: we're now using cgit for git repositories. Its fast and light, no official FastCGI support yet, but I hacked it into place during some experiments and discovered that it is indeed possible.]]>
        
    </content>
</entry>

<entry>
    <title>Web::SVN Problems</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/10/websvn-problems.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1294</id>

    <published>2008-10-25T21:29:06Z</published>
    <updated>2009-03-22T07:13:13Z</updated>

    <summary>Unfortunately, the newest Subversion Debian package has conflicts with Web::SVN. I&apos;ve hacked up the perl code to fix it, but there are still some parts of the SVN mirrors which are having problems. :-(Specifically, its the RA API: svn_ra_get_log: Assertion...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[Unfortunately, the newest Subversion Debian package has conflicts with Web::SVN. I've hacked up the perl code to fix it, but there are still some parts of the SVN mirrors which are having problems. :-(<br /><br />Specifically, its the RA API:<br /><br />

<a href="http://www.docunext.com/blog/2008/10/22/svn_ra_get_log-assertion-path-failed/">svn_ra_get_log: Assertion `*path != '/" failed

</a>]]>
        
    </content>
</entry>

<entry>
    <title>Useful</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/07/useful.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1293</id>

    <published>2008-07-19T15:44:35Z</published>
    <updated>2009-03-22T07:13:13Z</updated>

    <summary>When I setup these mirrors, I had a feeling that they were going to be useful. My goodness are they ever!Several times, I&apos;ve forked a file and am trying to fix a bug or modify behavior, and its so nice...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[When I setup these mirrors, I had a feeling that they were going to be useful. My goodness are they ever!<br /><br />Several times, I've forked a file and am trying to fix a bug or modify behavior, and its so nice to have an easily accessible reference point. <br /><br />Version control system and open source software is awesome!<br />]]>
        
    </content>
</entry>

<entry>
    <title>About these mirrors</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/04/about-these-mirrors.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1292</id>

    <published>2008-04-25T14:39:39Z</published>
    <updated>2009-03-22T07:13:13Z</updated>

    <summary>These mirrors are not actively maintained, meaning that they are likely out-of-date. They are also read-only, so no changes can be made by the public. For the most part, they contain no changes from the original sources, however, I would...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[These mirrors are not actively maintained, meaning that they are likely out-of-date. They are also read-only, so no changes can be made by the public. For the most part, they contain no changes from the original sources, however, I would always go upstream to the original authors for the source code. <br /><br />Why are these mirrors here? I enjoy browsing code and wanted a convenient way to do so. Voila - the Docunext Mirrors. Feel free to browse as much as you like, however, automated access is not allowed. <br />]]>
        
    </content>
</entry>

<entry>
    <title>Git Mirrors</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/04/git-mirrors.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1291</id>

    <published>2008-04-23T03:04:42Z</published>
    <updated>2009-03-22T07:13:12Z</updated>

    <summary>I&apos;ve added a directory for git mirrors, and am planning to do the same for mercurial mirrors. Enjoy! Git Mirrors...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[I've added a directory for git mirrors, and am planning to do the same for mercurial mirrors. Enjoy! 
<br/><br/>
<a href="/git-web/">Git Mirrors</a>]]>
        
    </content>
</entry>

<entry>
    <title>The Mirrors</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/04/the-mirrors.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1290</id>

    <published>2008-04-13T02:14:08Z</published>
    <updated>2009-03-22T07:13:12Z</updated>

    <summary>Without further ado, the mirrors: Docunext Mirrors...</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        <![CDATA[Without further ado, the mirrors:<br /><br />

<a href="/cgi-bin/">Docunext Mirrors</a>]]>
        
    </content>
</entry>

<entry>
    <title>For Browsing</title>
    <link rel="alternate" type="text/html" href="http://www.mirrors.docunext.com/blog/2008/04/for-browsing.html" />
    <id>tag:www.mirrors.docunext.com,2008:/blog//184.1289</id>

    <published>2008-04-12T17:16:47Z</published>
    <updated>2009-03-22T07:13:11Z</updated>

    <summary>I&apos;m setting up this sub-domain for browsing the source code of some of my favorite projects. If at some point I decide to make any changes, I&apos;ll fork the project or contribute the changes directly back to the project....</summary>
    <author>
        <name>Albert</name>
        
    </author>
    
    <category term="svn" label="svn" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.mirrors.docunext.com/blog/">
        I&apos;m setting up this sub-domain for browsing the source code of some of my favorite projects. If at some point I decide to make any changes, I&apos;ll fork the project or contribute the changes directly back to the project.
        
    </content>
</entry>

</feed>

