# Automatic reload of plugins

**URL:** <https://www.ruby-forum.com/t/automatic-reload-of-plugins/135477>\
**Category:** Rails\
**Created:** [April 22, 2008, 4:11pm UTC](https://www.ruby-forum.com/t/automatic-reload-of-plugins/135477 "2008-04-22T16:11:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![makire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/fbc32d/32.png) [@makire](https://www.ruby-forum.com/u/makire)\
**Post date:** [April 22, 2008, 4:11pm UTC](https://www.ruby-forum.com/t/automatic-reload-of-plugins/135477/1 "2008-04-22T16:11:36Z")

</div>

Hi

I am developing a plugin and wonder if there is a way to tell Mongrel  
to reload the vendor directory without restarting.

Many thanks in advance

/Erik L.

---

<div class="post-metadata">

**Author:** ![makire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/fbc32d/32.png) [@makire](https://www.ruby-forum.com/u/makire)\
**Post date:** [April 22, 2008, 4:25pm UTC](https://www.ruby-forum.com/t/automatic-reload-of-plugins/135477/2 "2008-04-22T16:25:19Z")

</div>

On 22 Apr 2008, at 15:10, Erik L. wrote:

> Hi
> 
> I am developing a plugin and wonder if there is a way to tell Mongrel  
> to reload the vendor directory without restarting.

It’s not really mongrel’s responsability. Removing the plugin’s lib  
directory from Dependencies.load\_once\_paths should help (unless you’re  
messing around with the plugin startup (ie it’s init.rb), in which  
case you may just be screwed unless you can convince rails to rerun  
it’s plugin loading process.

Fred

---

<div class="post-metadata">

**Author:** ![makire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/fbc32d/32.png) [@makire](https://www.ruby-forum.com/u/makire)\
**Post date:** [April 22, 2008, 8:49pm UTC](https://www.ruby-forum.com/t/automatic-reload-of-plugins/135477/3 "2008-04-22T20:49:22Z")

</div>

Erik L. wrote:

> Hi
> 
> I am developing a plugin and wonder if there is a way to tell Mongrel  
> to reload the vendor directory without restarting.

If you hook unit tests to that plugin, you can generally trigger the  
tests from  
a “messenger test” in your ./test folder. Then you can make small  
changes to the  
plugin, run the tests, and watch the results, without excess manual  
testing.

–  
Phlip