# Rake gems install with local .gem files

**URL:** <https://www.ruby-forum.com/t/rake-gems-install-with-local-gem-files/196780>\
**Category:** Deployment\
**Created:** [August 13, 2008, 10:12pm UTC](https://www.ruby-forum.com/t/rake-gems-install-with-local-gem-files/196780 "2008-08-13T22:12:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gsterndale](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/4bbf92/32.png) [@gsterndale](https://www.ruby-forum.com/u/gsterndale)\
**Post date:** [August 13, 2008, 10:12pm UTC](https://www.ruby-forum.com/t/rake-gems-install-with-local-gem-files/196780/1 "2008-08-13T22:12:25Z")

</div>

Hi All,

I’d like to take advantage of Rails 2.1 config.gem and rake gems  
install when deploying (with Capistrano). Unfortunately, outgoing HTTP  
is blocked in our production environment.

I’m considering keeping a directory of all required .gem files in our  
repository and after exporting the repo on the server, pointing gem to  
them with a .gemrc config file, but I haven’t been able to figure out  
how to do so.

Does anyone know how to do this?

Any alternate ideas?

Thanks!

---

<div class="post-metadata">

**Author:** ![gsterndale](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/4bbf92/32.png) [@gsterndale](https://www.ruby-forum.com/u/gsterndale)\
**Post date:** [August 13, 2008, 11:28pm UTC](https://www.ruby-forum.com/t/rake-gems-install-with-local-gem-files/196780/2 "2008-08-13T23:28:35Z")

</div>

I’ve used the gemsonrails [http://gemsonrails.rubyforge.org/](http://gemsonrails.rubyforge.org/) plugin to  
do  
something like this. It puts your gems in vendor/gems, which you can  
then  
check into your repository.

On Tue, Aug 12, 2008 at 9:56 AM, gsterndale [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> how to do so.
> 
> Does anyone know how to do this?
> 
> Any alternate ideas?
> 
> Thanks!
> 
> >

## –

Andrew S. \* [http://semprebon.blogspot.com/](http://semprebon.blogspot.com/)
