# Vendor Everything & Rake

**URL:** <https://www.ruby-forum.com/t/vendor-everything-rake/131281>\
**Category:** Rails\
**Created:** [March 7, 2008, 4:44pm UTC](https://www.ruby-forum.com/t/vendor-everything-rake/131281 "2008-03-07T16:44:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fuzzy66](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/a698b9/32.png) [@fuzzy66](https://www.ruby-forum.com/u/fuzzy66)\
**Post date:** [March 7, 2008, 4:44pm UTC](https://www.ruby-forum.com/t/vendor-everything-rake/131281/1 "2008-03-07T16:44:50Z")

</div>

We are considering moving our app to a “vendor everything” model:

> **[Vendor Everything — err.the\_blog](http://errtheblog.com/posts/50-vendor-everything)**
>
> Err the Blog: Ruby and Rails from the front.

I’m able to get the application to work fine this way, but, rake tasks  
don’t work unless I have the gems installed. Some of our rake tasks  
use the same libraries that the app does.

What I’d like is a way to do “vendor everything” that has 1 step for  
setting up an environment - just check out from the repository and run  
“rake”.

Am I expecting too much of the “vendor everything” approach? I presume  
this is some sort of load path issue? What is the right way to address  
this? Thanks.

Mike

Mike H.  
Program Manager, Collaborative Software Initiative  
removed\_email\_address@domain.invalid  
[http://www.csinitiative.com](http://www.csinitiative.com)
