http://forums.pragprog.com/forums/44/topics/369 en-us 60 <p><span class="caps">DOH</span>! This is already documented in the errata for the book.</p> <p><a href="http://books.pragprog.com/titles/fr_deploy/errata">http://books.pragprog.com/titles/fr_deploy/errata</a></p> Tue, 15 Apr 2008 21:51:13 -0000 forums.pragprog.com:44:369:2595 Brian Doll http://forums.pragprog.com/forums/44/topics/369 <p>As some others have noted, there may likely be some sections of this book that are effected by differences in Rails 2. I just bought the book an hour ago or so, but I just stumbled on what might be the first of such instances and thought I&#8217;d bring it up.</p> <p>In &#8220;Locking Down Plug-ins and Gems&#8221;, the advice is to pull the contents of a gem&#8217;s lib directory out into the vendor directory of a Rails app. In Rails 2 (and prior, for some) I would guess that the correct advice is to commit the gems under /vendor/gems, such that you may have /vendor/gems/foo-1.2.3 and /vendor/gems/bar-1.2.2.</p> <p>This is made possible by the environment.rb load_paths configuration which iterates over /vendor/gems directories and includes each of their lib directories during startup. Additionally, this makes for a much cleaner /vendor directory, with more clarity around what files belong to what gem.</p> <p>Looking forward to reading the rest of the book! <br />cheers,<br />b</p> Tue, 15 Apr 2008 21:08:20 -0000 forums.pragprog.com:44:369:2594 Brian Doll http://forums.pragprog.com/forums/44/topics/369