Bryan Helmkamp - Scourging your Ruby code with Flog Commentstag:www.brynary.com,2009:/2007/9/13/scourging-your-ruby-code-with-flog/commentsMephisto Drax2007-09-19T05:24:19ZAbhay Kumartag:www.brynary.com,2007-09-13:899:9052007-09-18T01:18:25Z2007-09-18T01:18:25ZComment on 'Scourging your Ruby code with Flog' by Abhay Kumar<p>This is great. One small thing: you should probably check for the directory first before writing to a file in there.</p>Joshua Nicholstag:www.brynary.com,2007-09-13:899:9042007-09-17T05:15:47Z2007-09-17T05:15:47ZComment on 'Scourging your Ruby code with Flog' by Joshua Nichols<p>When I first ran this, I was getting:
nichoj@metaverse ~/projects/technicalpickles.com $ rake flog
(in /home/nichoj/projects/technicalpickles.com)
rake aborted!
No such file or directory – /home/nichoj/projects/technicalpickles.com/config/../tmp/flog/all.txt</p>
<pre><code>(See full trace by running task with --trace)</code></pre>
<p>So, in the flog method, we should be doing a mkdir. I added this bit to it:
Dir.mkdir ”#{RAILS_ROOT}/tmp/flog”</p>
<p>Worked like a charm after that.</p>
<p>I wonder, do you think this is something that this is something that could be contributed back to flog?</p>Luke Meliatag:www.brynary.com,2007-09-13:899:9002007-09-13T05:58:10Z2007-09-13T05:58:10ZComment on 'Scourging your Ruby code with Flog' by Luke Melia<p>Cool, Bryan. You should add your sake task to sakebar [http://sakebar.railsrumble.com/]</p>