<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>themattharris.com &#187; mt</title>
	<atom:link href="http://themattharris.com/tag/mt/feed/" rel="self" type="application/rss+xml" />
	<link>http://themattharris.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 01 Jun 2010 17:30:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Generating an SSH Keypair</title>
		<link>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Fgenerating-an-ssh-keypair%2F&amp;seed_title=Generating+an+SSH+Keypair</link>
		<comments>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Fgenerating-an-ssh-keypair%2F&amp;seed_title=Generating+an+SSH+Keypair#comments</comments>
		<pubDate>Wed, 06 Aug 2008 08:46:56 +0000</pubDate>
		<dc:creator>themattharris</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[SysAdmin]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[keypair]]></category>
		<category><![CDATA[mediatemple]]></category>
		<category><![CDATA[mt]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://www.themattharris.com/?p=18</guid>
		<description><![CDATA[This is part 2 of a 4 part series of setting up your systems to use Git but in this case, is of general interest to those who may need to generate SSH Keypairs. Git uses SSH key pairs to authenticate the machine you are accessing the repository from with the place you store that [...]]]></description>
			<content:encoded><![CDATA[<p>This is part 2 of a 4 part series of setting up your systems to use Git but in this case, is of general interest to those who may need to generate SSH Keypairs.</p>

<p>Git uses SSH key pairs to authenticate the machine you are accessing the repository from with the place you store that repository.  If you followed the post about installing Git on your MediaTemple server then this is the next step in getting Git ready.  This post should also act as a quick reference if you are not yet familiar with, or just want reminding of, the method of creating SSH public keypairs.<span id="more-18"></span></p>

<h2>What you will need</h2>

<ul>
<li>SSH root access to your server (MediaTemple offer this though the <a href="http://ac.mediatemple.net">Account Center</a>)</li></li>
<li>About 5 minutes of time</li>
</ul>

<h2>Method</h2>

<p>This is a quick process and remarkably easy to do.</p>

<ol>
<li>Log into your server using SSH. Usually this is <code>ssh root@your-domain.com</code></li>
<li>Enter the command: <code>ssh-keygen -t rsa</code></li>
<li>You will be asked where you want to save the key file, just press enter. (If you are told the file already exists skip the next 2 steps)</li>
<li>You&#8217;ll now be asked to enter a passphrase . You should enter a passphrase you will remember here as you will need it when you communicate with the main repository from now on.</li>
<li>Confirm the passphrase.</li>
<li>You can view the public keypair that was just created by entering: <code>cat ~/.ssh/id_rsa.pub</code></li>
</ol>

<p>That&#8217;s all, in the next post i&#8217;ll show you how to connect to your repository on Unfuddle.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Fgenerating-an-ssh-keypair%2F&amp;seed_title=Generating+an+SSH+Keypair/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Installing Git binaries onto a MediaTemple server</title>
		<link>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Finstalling-git-binaries-onto-a-mediatemple-server%2F&amp;seed_title=Installing+Git+binaries+onto+a+MediaTemple+server</link>
		<comments>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Finstalling-git-binaries-onto-a-mediatemple-server%2F&amp;seed_title=Installing+Git+binaries+onto+a+MediaTemple+server#comments</comments>
		<pubDate>Wed, 06 Aug 2008 08:27:21 +0000</pubDate>
		<dc:creator>themattharris</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[SysAdmin]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[mediatemple]]></category>
		<category><![CDATA[mt]]></category>

		<guid isPermaLink="false">http://www.themattharris.com/?p=29</guid>
		<description><![CDATA[This is part 1 of a series on setting up your systems to use Git. As a developer I make frequent use of version control systems to keep my code safe and easily keep production sites up to date. I previously used the widely supported SVN but have recently moved to the open source project [...]]]></description>
			<content:encoded><![CDATA[<p>This is part 1 of a series on setting up your systems to use Git.</p>

<p>As a developer I make frequent use of version control systems to keep my code safe and easily keep production sites up to date.  I previously used the widely supported <a href="http://subversion.tigris.org/">SVN</a> but have recently moved to the open source project <a href="http://git.or.cz/">Git</a>.  This move hasn&#8217;t been without it&#8217;s problems though and one of the largest was that Git wasn&#8217;t installed on my MediaTemple (<abbr title="MediaTemple">MT</abbr>) servers. Luckily, I found an MT knowledge base article titled <a href="http://kb.mediatemple.net/questions/820/Installing+Git+on+a+(dv)+3.5+server" title="MediaTemple knowledge base article">&#8220;Installing Git on a (dv) 3.5 server&#8221;</a> but soon found it had a couple of holes in it which prevented a successful install.</p>

<p>So, in case you find yourself in the same boat, I present my method for installing Git on a MediaTemple Dedicated Virtual 3.5 Server.<span id="more-29"></span></p>

<p>This method may work on other providers servers; if it does drop me a comment and i&#8217;ll update the post.  What I can tell you is this method is for CentOS 5 and will not work on a MediaTemple dv3 (it&#8217;s running Centos 4).</p>

<p>These steps are provided as a guide only and you follow them at your own risk.</p>

<h2>What you will need</h2>

<ol>
<li>SSH root access to your server (MediaTemple offer this though the <a href="http://ac.mediatemple.net">Account Center</a></li>
<li>Developer tools installed on your server (MediaTemple offer this though the <a href="http://ac.mediatemple.net">Account Center</a></li>
<li>An empty text document to save some links into</li>
<li>About 30 minutes of time (after backing up)</li>
</ol>

<h2>Method</h2>

<ol>
<li><strong>Ensure you have a backup of your server</strong></li>
<li>Using your favourite web browser navigate to <a href="http://mirror.centos.org/centos/5/os/i386/CentOS/">http://mirror.centos.org/centos/5/os/i386/CentOS/</a>, this address is case sensitive</li>
<li>You&#8217;ll see a whole list of packages which you can install. The ones you need to locate the current links for are:

<ul>
<li>python-iniparse <a href="http://mirror.centos.org/centos/5/os/i386/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm">http://mirror.centos.org/centos/5/os/i386/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm</a></li>
<li><abbr title="yellowdog updater modified">yum</abbr> <a href="http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.8-9.el5.centos.1.noarch.rpm">http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.8-9.el5.centos.1.noarch.rpm</a>
Copy the URLs into a text document as we will need them later.  The URLs given here were correct at the time of posting this article so may be wrong now as the version numbers change. To find the packages quickly search the page for the names i&#8217;ve given, e.g. python-iniparse</li>
</ul></li>
<li>Log into your server using SSH. 
<pre class="brush: plain;">ssh root@your-domain.com</pre></li>
<li>Install the python-iniparse package by entering the command: (replace with the URL you copied earlier): 
<pre class="brush: plain;">rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm</pre></li>
<li>Install yum by entering the command: (replace with the URL you copied earlier)
<pre class="brush: plain;">rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.8-9.el5.centos.1.noarch.rpm</pre></li>
<li>The last rpm we need is EPEL. Install this by entering: <pre class="brush: plain;">rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-2.noarch.rpm</pre></li>
<li>yum is now installed, making things a lot easier</li>
<li>Tell yum to update itself and everything it knows about by entering the command: 
<pre class="brush: plain;">yum -y update</pre></li>
<li>When yum has finished updating, we can install Git. Simply enter: 
<pre class="brush: plain;">yum install git</pre> and answer <code>y</code> to the prompts</li>
</ol>

<p>Git is now successfully installed on your MediaTemple server ready for use. Next post is about <a href="/2008/08/06/generating-an-ssh-keypair/">Generating an SSH keypair</a> which you need to access your remote repository.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.themattharris.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fthemattharris.com%2F2008%2F08%2Finstalling-git-binaries-onto-a-mediatemple-server%2F&amp;seed_title=Installing+Git+binaries+onto+a+MediaTemple+server/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
