http://blog.randomutterings.com/articles/tag/peepcode en-us 40 <p>OK, let me start off by saying, I love the tutorials from peepcode, you guys are doing a great job so keep doing it.</p> <p>Alas, I got stuck while watching the <a href="http://peepcode.com/products/test-first-development">Test-first-development</a> tutorial. They were using <a href="http://rapt.rubyforge.org/">Rapt</a> as an alternative to script/plugin and when I tried to run it I kept getting an error.</p> <blockquote> <p>Error: RaPT currently does not work outside of a Rails application directory. Please change to the top level of a Rails application and try again.</p> </blockquote> <p>This error is misleading but at least it was obviously misleading, after all I know I'm in my Rails application directory.</p> <p>After some googling, I found a post describing a work around for the problem, but it basically gave instructions on installing the plugin with script/plugin. But the guys at peepcode had a reason for using rapt over script/plugin (its faster). So I Google some more. I finally find a <a href="http://rubyforge.org/tracker/index.php?func=detail&aid=6611&group_id=1889&atid=7384">bug </a> on the Rapt <a href="http://rubyforge.org/projects/rapt/">Trac</a> posted in 2006 that explains that the user must first add repositories by executing the following.</p> <pre> <p>rapt discover</p> </pre> <p>If anyone knows how to have it default to yes without prompting you for every repository, please post a comment.</p> <p>Alternatively, you can add only the repositories you want to use by executing the following.</p> <pre> <p>rapt source http://path-to-repository</p> </pre> Thu, 13 Sep 2007 12:47:00 -0400 urn:uuid:a5ba1b07-1d85-4136-9454-4820007eb561 Chris Barnes http://blog.randomutterings.com/articles/2007/09/13/rapt-error-during-peepcodes-test-first-development-tutorial Ruby ruby rails rapt plugins peepcode tutorial screencast http://blog.randomutterings.com/articles/trackback/22