<?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"
	>
<channel>
	<title>Comments for Tim Dysinger</title>
	<atom:link href="http://dysinger.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://dysinger.net</link>
	<description>Notes on Life, 'Puters and Hawaii</description>
	<pubDate>Fri, 04 Jul 2008 03:58:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Installing Apache and mod_rails on Mac OS X Leopard by dysinger</title>
		<link>http://dysinger.net/2008/04/14/installing-apache-and-mod_rails-on-mac-os-x-leopard/#comment-1013</link>
		<dc:creator>dysinger</dc:creator>
		<pubDate>Wed, 25 Jun 2008 20:21:20 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=80#comment-1013</guid>
		<description>For development on your laptop, you basically just need a /etc/hosts that has something like this:

&lt;pre&gt;
127.0.0.1 localhost myapp.com sub.myapp.com sub2.myapp.com
&lt;/pre&gt;

replace "sub" and "sub1" with your test subdomains (if you even need subdomains).  Add as many as you like.  unfortunately you cannot have wildcards in /etc/hosts so you have to list all your test subdomains.
</description>
		<content:encoded><![CDATA[<p>For development on your laptop, you basically just need a /etc/hosts that has something like this:</p>
<pre>
127.0.0.1 localhost myapp.com sub.myapp.com sub2.myapp.com
</pre>
<p>replace &#8220;sub&#8221; and &#8220;sub1&#8243; with your test subdomains (if you even need subdomains).  Add as many as you like.  unfortunately you cannot have wildcards in /etc/hosts so you have to list all your test subdomains.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deploying with Capistrano, Git and SSH-Agent by dysinger</title>
		<link>http://dysinger.net/2008/04/30/deploying-with-capistrano-git-and-ssh-agent/#comment-1012</link>
		<dc:creator>dysinger</dc:creator>
		<pubDate>Wed, 25 Jun 2008 20:08:32 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=83#comment-1012</guid>
		<description>Capistrano often asks for a password for sudo when it really doesn't need to if your deploy user already has the permissions needed.  I use

&lt;pre&gt;
set :run_method, :run
&lt;/pre&gt;

It stops asking for sudo passwords by default.  This what my current app looks like:

&lt;pre&gt;
set :application, "myrailsapp"
set :user, 'deploy'
set :scm, :git
set :run_method, :run
set :ssh_options, { :forward_agent =&gt; true }
set :repository, "git@XXXX.com:blahblah/#{application}.git"
set :deploy_via, :remote_cache
set :deploy_to, "/var/apps/#{application}"
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Capistrano often asks for a password for sudo when it really doesn&#8217;t need to if your deploy user already has the permissions needed.  I use</p>
<pre>
set :run_method, :run
</pre>
<p>It stops asking for sudo passwords by default.  This what my current app looks like:</p>
<pre>
set :application, "myrailsapp"
set :user, 'deploy'
set :scm, :git
set :run_method, :run
set :ssh_options, { :forward_agent => true }
set :repository, "git@XXXX.com:blahblah/#{application}.git"
set :deploy_via, :remote_cache
set :deploy_to, "/var/apps/#{application}"
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deploying with Capistrano, Git and SSH-Agent by AK</title>
		<link>http://dysinger.net/2008/04/30/deploying-with-capistrano-git-and-ssh-agent/#comment-1011</link>
		<dc:creator>AK</dc:creator>
		<pubDate>Mon, 23 Jun 2008 17:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=83#comment-1011</guid>
		<description>Where, where, where can I find out how to set up an SSH key and put it on my server so that I don't have to type the password any more?  I have copied the id_rsa file to .ssh/authorized_keys on the server.  I have set the permissions.

I added the key to the agent.  Of course that means I have to type "exec ssh-agent bash" every time I go the the shell now, for whatever stupid reason.  It's not clear.  I can't find out why, anywhere, I have to do that now.

But even when I do that, Capistrano FORCES me to put in the stupid password.  God, I am SO MAD.  It's always the stupidest things that take the longest.  2 hours now, how ridiculous.</description>
		<content:encoded><![CDATA[<p>Where, where, where can I find out how to set up an SSH key and put it on my server so that I don&#8217;t have to type the password any more?  I have copied the id_rsa file to .ssh/authorized_keys on the server.  I have set the permissions.</p>
<p>I added the key to the agent.  Of course that means I have to type &#8220;exec ssh-agent bash&#8221; every time I go the the shell now, for whatever stupid reason.  It&#8217;s not clear.  I can&#8217;t find out why, anywhere, I have to do that now.</p>
<p>But even when I do that, Capistrano FORCES me to put in the stupid password.  God, I am SO MAD.  It&#8217;s always the stupidest things that take the longest.  2 hours now, how ridiculous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Replacing Braid or Piston (for Git) with 40 lines of Rake by Anton</title>
		<link>http://dysinger.net/2008/04/29/replacing-braid-or-piston-for-git-with-40-lines-of-rake/#comment-1010</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Mon, 09 Jun 2008 10:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=91#comment-1010</guid>
		<description>Cheers Tim! I figured it out after a bit of fiddling and guesswork.

Nice work overall with the script. It really helps git noobies like myself make the transition over to git from svn + piston. Your solution definitely looks to be the cleanest and simplest.

The best thing about it is I can see exactly what commands you are issuing to git so in time, when my git knowledge starts to expand, I'll actually be able to understand what the hell is going on! In the mean time I can just be content that it all works as advertised.

Cheers!

p.s I know this is a sake issue but you might be able to help - is it possible to tell sake to update the script? At the moment I'm removing the tasks one by one and then reinstalling the script. Is there a cleaner way to do this? I've checked sake --help and nothing jumped out at me.</description>
		<content:encoded><![CDATA[<p>Cheers Tim! I figured it out after a bit of fiddling and guesswork.</p>
<p>Nice work overall with the script. It really helps git noobies like myself make the transition over to git from svn + piston. Your solution definitely looks to be the cleanest and simplest.</p>
<p>The best thing about it is I can see exactly what commands you are issuing to git so in time, when my git knowledge starts to expand, I&#8217;ll actually be able to understand what the hell is going on! In the mean time I can just be content that it all works as advertised.</p>
<p>Cheers!</p>
<p>p.s I know this is a sake issue but you might be able to help - is it possible to tell sake to update the script? At the moment I&#8217;m removing the tasks one by one and then reinstalling the script. Is there a cleaner way to do this? I&#8217;ve checked sake &#8211;help and nothing jumped out at me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Replacing Braid or Piston (for Git) with 40 lines of Rake by dysinger</title>
		<link>http://dysinger.net/2008/04/29/replacing-braid-or-piston-for-git-with-40-lines-of-rake/#comment-1009</link>
		<dc:creator>dysinger</dc:creator>
		<pubDate>Sun, 08 Jun 2008 05:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=91#comment-1009</guid>
		<description>@Anton,

Good catch - I had changed the name of a task but not corrected the example usage.  I have changed it to be correct now.  I also added another task for looking at the diff of the remote vs what's been previously integrated.

-Tim</description>
		<content:encoded><![CDATA[<p>@Anton,</p>
<p>Good catch - I had changed the name of a task but not corrected the example usage.  I have changed it to be correct now.  I also added another task for looking at the diff of the remote vs what&#8217;s been previously integrated.</p>
<p>-Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Replacing Braid or Piston (for Git) with 40 lines of Rake by Brian Donovan</title>
		<link>http://dysinger.net/2008/04/29/replacing-braid-or-piston-for-git-with-40-lines-of-rake/#comment-1008</link>
		<dc:creator>Brian Donovan</dc:creator>
		<pubDate>Thu, 05 Jun 2008 18:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=91#comment-1008</guid>
		<description>I recommend checking out Thor. It's kinda like Rake, but actually testable and has installed tasks like Sake:

http://github.com/wycats/thor</description>
		<content:encoded><![CDATA[<p>I recommend checking out Thor. It&#8217;s kinda like Rake, but actually testable and has installed tasks like Sake:</p>
<p><a href="http://github.com/wycats/thor" rel="nofollow">http://github.com/wycats/thor</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing Apache and mod_rails on Mac OS X Leopard by Bryce</title>
		<link>http://dysinger.net/2008/04/14/installing-apache-and-mod_rails-on-mac-os-x-leopard/#comment-1007</link>
		<dc:creator>Bryce</dc:creator>
		<pubDate>Wed, 04 Jun 2008 21:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=80#comment-1007</guid>
		<description>could you post your /etc/hosts file? I've got everything working up to there. Thanks a lot for the post.</description>
		<content:encoded><![CDATA[<p>could you post your /etc/hosts file? I&#8217;ve got everything working up to there. Thanks a lot for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiling Erlang on Mac OS X Leopard from Scratch by links for 2008-06-01 at Topper&#8217;s Blog</title>
		<link>http://dysinger.net/2007/12/20/compiling-erlang-on-mac-os-x-leopard-from-scratch/#comment-1006</link>
		<dc:creator>links for 2008-06-01 at Topper&#8217;s Blog</dc:creator>
		<pubDate>Sun, 01 Jun 2008 04:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/2007/12/20/compiling-erlang-on-mac-os-x-leopard-from-scratch/#comment-1006</guid>
		<description>[...] Tim Dysinger » Compiling Erlang on Mac OS X Leopard from Scratch (tags: erlang install leopard source tutorial howto) [...]</description>
		<content:encoded><![CDATA[<p>[...] Tim Dysinger » Compiling Erlang on Mac OS X Leopard from Scratch (tags: erlang install leopard source tutorial howto) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Replacing Braid or Piston (for Git) with 40 lines of Rake by Anton</title>
		<link>http://dysinger.net/2008/04/29/replacing-braid-or-piston-for-git-with-40-lines-of-rake/#comment-1005</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Wed, 28 May 2008 18:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/?p=91#comment-1005</guid>
		<description>I'm a bit lost - where is the git:subtree:add task? It's listed in the usage but not actually in the code.

Cheers

Anton</description>
		<content:encoded><![CDATA[<p>I&#8217;m a bit lost - where is the git:subtree:add task? It&#8217;s listed in the usage but not actually in the code.</p>
<p>Cheers</p>
<p>Anton</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing GIT on Mac OS X 10.5 Leopard by leonardofaria.net &#8594; Rails, Git, MySQL e mod_rails no Leopard</title>
		<link>http://dysinger.net/2007/12/30/installing-git-on-mac-os-x-105-leopard/#comment-1004</link>
		<dc:creator>leonardofaria.net &#8594; Rails, Git, MySQL e mod_rails no Leopard</dc:creator>
		<pubDate>Sat, 24 May 2008 16:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://dysinger.net/2007/12/30/installing-git-on-mac-os-x-105-leopard/#comment-1004</guid>
		<description>[...] o download do pacote e apertar &#8216;next&#8217;, &#8216;next&#8217;, &#8216;finish&#8217;. Para instalação via shell é necessário compilar o GIT e outras coisinhas [...]</description>
		<content:encoded><![CDATA[<p>[...] o download do pacote e apertar &#8216;next&#8217;, &#8216;next&#8217;, &#8216;finish&#8217;. Para instalação via shell é necessário compilar o GIT e outras coisinhas [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
