Permalink
Browse files

Site updated at 2013-09-04 18:33:39 UTC

  • Loading branch information...
1 parent 39c81cc commit 24c76133d65eb71b66c0e6a53c5e6109716fdc2d @benhamill committed Sep 4, 2013
Showing with 16 additions and 16 deletions.
  1. +4 −4 2013/09/03/never-type-bundle-exec-again/index.html
  2. +5 −5 atom.xml
  3. +4 −4 index.html
  4. +3 −3 sitemap.xml
@@ -96,7 +96,7 @@ <h1 class="entry-title">Never Type Bundle Exec Again</h1>
<div class="entry-content"><p>Sometimes people complain about having to type <code>bundle exec</code> before every
freakin&#39; command in a Ruby project. Honestly, I think the benefits Bundler gives
-you outweigh that down side by a <em>huge</em> margin. However, there is good news: You
+you outweigh that downside by a <em>huge</em> margin. However, there is good news: You
can use this one weird trick to never type <code>bundle exec</code> again.</p>
<p>OK. It&#39;s actually an option of two weird tricks. And then a bonus trick. This
@@ -105,7 +105,7 @@ <h1 class="entry-title">Never Type Bundle Exec Again</h1>
<h2>Somewhat Involved, Works Everywhere</h2>
<p>If you&#39;ve got Ruby installed, you can do this trick. It&#39;s a little hacky and
-comes with some down sides.</p>
+comes with some downsides.</p>
<p>First up, make <code>~/.bundle/config</code> look like this business:</p>
@@ -129,7 +129,7 @@ <h1 class="entry-title">Never Type Bundle Exec Again</h1>
</pre></td><td class='code'><pre><code class='text'><span class='line'>bin
</span></code></pre></td></tr></table></div></figure>
-<p>Here&#39;s down side number one: You will probably have to override this for specific
+<p>Here&#39;s downside number one: You will probably have to override this for specific
projects. For instance, gems often ship with a <code>bin</code> directory with files to do
with the gem. You&#39;ll want to make sure those aren&#39;t ignored. If you explicitly
<code>git add</code> them, they should be tracked by git thereafter, but you have to go out
@@ -141,7 +141,7 @@ <h1 class="entry-title">Never Type Bundle Exec Again</h1>
<p>At this point, you could stop, except you&#39;d have to type <code>bin/</code> in front of
every command, instead of <code>bundle exec</code>. Sure, it&#39;s shorter, but still annoying.
The next thing to do might be to prepend <code>./bin</code> to your <code>$PATH</code> so that your
-command line looks there for commands first. Down side number two is that there
+command line looks there for commands first. Downside number two is that there
are some negative security implications to this, so I for sure don&#39;t recommend
it for servers, but I&#39;ll leave it up to you whether you do it on your personal
dev machine.</p>
View
@@ -4,7 +4,7 @@
<title><![CDATA[Garbled]]></title>
<link href="http://garbled.benhamill.com/atom.xml" rel="self"/>
<link href="http://garbled.benhamill.com/"/>
- <updated>2013-09-04T13:23:40-05:00</updated>
+ <updated>2013-09-04T13:33:37-05:00</updated>
<id>http://garbled.benhamill.com/</id>
<author>
<name><![CDATA[Ben Hamill]]></name>
@@ -20,7 +20,7 @@
<id>http://garbled.benhamill.com/2013/09/03/never-type-bundle-exec-again</id>
<content type="html"><![CDATA[<p>Sometimes people complain about having to type <code>bundle exec</code> before every
freakin&#39; command in a Ruby project. Honestly, I think the benefits Bundler gives
-you outweigh that down side by a <em>huge</em> margin. However, there is good news: You
+you outweigh that downside by a <em>huge</em> margin. However, there is good news: You
can use this one weird trick to never type <code>bundle exec</code> again.</p>
<p>OK. It&#39;s actually an option of two weird tricks. And then a bonus trick. This
@@ -29,7 +29,7 @@ joke is ruined.</p>
<h2>Somewhat Involved, Works Everywhere</h2>
<p>If you&#39;ve got Ruby installed, you can do this trick. It&#39;s a little hacky and
-comes with some down sides.</p>
+comes with some downsides.</p>
<p>First up, make <code>~/.bundle/config</code> look like this business:</p>
@@ -53,7 +53,7 @@ git ignore file and make sure it includes this:</p>
</pre></td><td class='code'><pre><code class='text'><span class='line'>bin
</span></code></pre></td></tr></table></div></figure>
-<p>Here&#39;s down side number one: You will probably have to override this for specific
+<p>Here&#39;s downside number one: You will probably have to override this for specific
projects. For instance, gems often ship with a <code>bin</code> directory with files to do
with the gem. You&#39;ll want to make sure those aren&#39;t ignored. If you explicitly
<code>git add</code> them, they should be tracked by git thereafter, but you have to go out
@@ -65,7 +65,7 @@ there.</p>
<p>At this point, you could stop, except you&#39;d have to type <code>bin/</code> in front of
every command, instead of <code>bundle exec</code>. Sure, it&#39;s shorter, but still annoying.
The next thing to do might be to prepend <code>./bin</code> to your <code>$PATH</code> so that your
-command line looks there for commands first. Down side number two is that there
+command line looks there for commands first. Downside number two is that there
are some negative security implications to this, so I for sure don&#39;t recommend
it for servers, but I&#39;ll leave it up to you whether you do it on your personal
dev machine.</p>
View
@@ -99,7 +99,7 @@ <h1 class="entry-title"><a href="/2013/09/03/never-type-bundle-exec-again/">Neve
<div class="entry-content"><p>Sometimes people complain about having to type <code>bundle exec</code> before every
freakin&#39; command in a Ruby project. Honestly, I think the benefits Bundler gives
-you outweigh that down side by a <em>huge</em> margin. However, there is good news: You
+you outweigh that downside by a <em>huge</em> margin. However, there is good news: You
can use this one weird trick to never type <code>bundle exec</code> again.</p>
<p>OK. It&#39;s actually an option of two weird tricks. And then a bonus trick. This
@@ -108,7 +108,7 @@ <h1 class="entry-title"><a href="/2013/09/03/never-type-bundle-exec-again/">Neve
<h2>Somewhat Involved, Works Everywhere</h2>
<p>If you&#39;ve got Ruby installed, you can do this trick. It&#39;s a little hacky and
-comes with some down sides.</p>
+comes with some downsides.</p>
<p>First up, make <code>~/.bundle/config</code> look like this business:</p>
@@ -132,7 +132,7 @@ <h1 class="entry-title"><a href="/2013/09/03/never-type-bundle-exec-again/">Neve
</pre></td><td class='code'><pre><code class='text'><span class='line'>bin
</span></code></pre></td></tr></table></div></figure>
-<p>Here&#39;s down side number one: You will probably have to override this for specific
+<p>Here&#39;s downside number one: You will probably have to override this for specific
projects. For instance, gems often ship with a <code>bin</code> directory with files to do
with the gem. You&#39;ll want to make sure those aren&#39;t ignored. If you explicitly
<code>git add</code> them, they should be tracked by git thereafter, but you have to go out
@@ -144,7 +144,7 @@ <h1 class="entry-title"><a href="/2013/09/03/never-type-bundle-exec-again/">Neve
<p>At this point, you could stop, except you&#39;d have to type <code>bin/</code> in front of
every command, instead of <code>bundle exec</code>. Sure, it&#39;s shorter, but still annoying.
The next thing to do might be to prepend <code>./bin</code> to your <code>$PATH</code> so that your
-command line looks there for commands first. Down side number two is that there
+command line looks there for commands first. Downside number two is that there
are some negative security implications to this, so I for sure don&#39;t recommend
it for servers, but I&#39;ll leave it up to you whether you do it on your personal
dev machine.</p>
View
@@ -142,19 +142,19 @@
</url>
<url>
<loc>http://garbled.benhamill.com/2013/09/03/never-type-bundle-exec-again/</loc>
- <lastmod>2013-09-04T13:23:24-05:00</lastmod>
+ <lastmod>2013-09-04T13:30:03-05:00</lastmod>
</url>
<url>
<loc>http://garbled.benhamill.com/about/</loc>
<lastmod>2013-09-04T09:55:06-05:00</lastmod>
</url>
<url>
<loc>http://garbled.benhamill.com/blog/archives/</loc>
- <lastmod>2013-09-04T13:23:24-05:00</lastmod>
+ <lastmod>2013-09-04T13:30:03-05:00</lastmod>
</url>
<url>
<loc>http://garbled.benhamill.com/</loc>
- <lastmod>2013-09-04T13:23:24-05:00</lastmod>
+ <lastmod>2013-09-04T13:30:03-05:00</lastmod>
</url>
<url>
<loc>http://garbled.benhamill.com/robots.txt</loc>

0 comments on commit 24c7613

Please sign in to comment.