<?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>Words by Rob</title>
	<atom:link href="https://blog.robtarr.net/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.robtarr.net</link>
	<description>robtarr.net</description>
	<lastBuildDate>Tue, 17 Nov 2015 00:10:16 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.3.1</generator>
	<item>
		<title>HTTPS All the Things!!</title>
		<link>https://blog.robtarr.net/https-all-the-things/</link>
		<comments>https://blog.robtarr.net/https-all-the-things/#comments</comments>
		<pubDate>Tue, 17 Nov 2015 00:10:16 +0000</pubDate>
		<dc:creator><![CDATA[rob]]></dc:creator>
		
		<guid isPermaLink="false">http://blog.robtarr.net/?p=30</guid>
		<description><![CDATA[Google recently announced that they would be using HTTPS as part of it&#8217;s search ranking algorithms. This is great for the web. The more secure every site is, the better off we are as a community. Recently, my friend Mike Yockey told me about letsencrypt.org. Let&#8217;s Encrypt is a free, open authority for SSL certificates [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><img src="http://blog.robtarr.net/wp-content/uploads/2015/11/HTTPS-AllTheThings.jpg" alt="HTTPS All The Things" width="400" height="300" class="aligncenter size-full wp-image-31" /></p>
<p><a href="http://googlewebmastercentral.blogspot.com/2014/08/https-as-ranking-signal.html">Google recently announced</a> that they would be using HTTPS as part of it&#8217;s search ranking algorithms. This is great for the web. The more secure every site is, the better off we are as a community. Recently, my friend <a href="http://mikeyockey.com/">Mike Yockey</a> told me about <a href="https://letsencrypt.org">letsencrypt.org</a>. Let&#8217;s Encrypt is a free, open authority for SSL certificates that just launched it&#8217;s private beta.</p>
<p>So, I signed up a few days ago got my authorization today. The email had a few quick, simple instructions to run the command line tool to generate the certificates, and about 5 minutes later:</p>
<p><img src="http://blog.robtarr.net/wp-content/uploads/2015/11/https_robtarr.png" alt="https_robtarr" width="200" height="62" class="aligncenter size-full wp-image-32" /></p>
<p>I would encourage everyone to look into this for sites they manage but have been prohibited (cost?) from securing with SSL. One thing to note, is that you&#8217;ll want to include all of your subdomains when you register, as currently in the beta, they need to be manually added to the whitelist &#8211; this is why this blog is not yet HTTPS. <img src="https://blog.robtarr.net/wp-includes/images/smilies/frownie.png" alt=":(" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
]]></content:encoded>
			<wfw:commentRss>https://blog.robtarr.net/https-all-the-things/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simplify Your Atom Config</title>
		<link>https://blog.robtarr.net/simplify-your-atom-config/</link>
		<comments>https://blog.robtarr.net/simplify-your-atom-config/#comments</comments>
		<pubDate>Sat, 24 Oct 2015 03:53:12 +0000</pubDate>
		<dc:creator><![CDATA[rob]]></dc:creator>
		
		<guid isPermaLink="false">http://blog.dev/?p=8</guid>
		<description><![CDATA[If you love setting up your editor to get it just right every time you set up a new computer, or really enjoy keeping plugins and setting in sync across multiple computers you should probably stop reading right now. OK, good, you stayed here – because you want to make this process simple and repeatable. Let&#8217;s do [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>If you love setting up your editor to get it just right every time you set up a new computer, or really enjoy keeping plugins and setting in sync across multiple computers you should probably stop reading right now.</p>
<p>OK, good, you stayed here – because you want to make this process simple and repeatable. Let&#8217;s do it.</p>
<h2>Step 1</h2>
<p>The first step is to setup a dotfiles repo. If you haven&#8217;t done this already, check this out <a href="https://dotfiles.github.io/">this example on GitHub.com</a>.</p>
<h2>Step 2</h2>
<p>Move <code>~/.atom</code> into your dotfiles repo. Mine is located at <code>~/my-projects/dotfiles/atom</code>.</p>
<h2>Step 3</h2>
<p>From the folder containing the original <code>.atom</code> folder, create a symlink to your new Atom config.</p>
<p>Mac OS X/Linux:</p>
<pre><code>cd ~
ln -s ~/my-projects/dotfiles/atom .atom
</code></pre>
<p>Windows:</p>
<pre><code>cd C:\Users\&lt;user&gt;\.atom
mklink /D my-projects\dotfiles\atom .atom
</code></pre>
<h2>Step 4</h2>
<p>Inside your new atom folder, you will probably want to add a <code>.gitignore</code> file. This will keep your repo from getting bloated. Here&#8217;s what mine looks like:</p>
<pre><code>.apm
.node-gyp
compile-cache
packages
storage
</code></pre>
<h2>Step 5</h2>
<p>I&#8217;m using <a href="https://atom.io/packages/parcel">Parcel</a> to keep track of my plugins. Running <code>Parcel: sync</code> will generate a <code>package.cson</code> file in your <code>.atom</code> folder, and install any missing plugins.</p>
<h2>Step 6</h2>
<p>Commit the changes to your dotfiles repo and push them to GitHub (or wherever your repo is).</p>
<h2>That&#8217;s it.</h2>
<p>Next time you need to set up Atom on another computer, clone your dotfiles, recreate the symlink, and you&#8217;re good to go.</p>
]]></content:encoded>
			<wfw:commentRss>https://blog.robtarr.net/simplify-your-atom-config/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
