# Avoiding restarting WEBrick while developing acts\_as plugin

**URL:** <https://www.ruby-forum.com/t/avoiding-restarting-webrick-while-developing-acts-as-plugin/47537>\
**Category:** Rails\
**Created:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/avoiding-restarting-webrick-while-developing-acts-as-plugin/47537 "2005-11-12T12:49:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![petermichaux](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/46a35a/32.png) [@petermichaux](https://www.ruby-forum.com/u/petermichaux)\
**Post date:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/avoiding-restarting-webrick-while-developing-acts-as-plugin/47537/1 "2005-11-12T12:49:21Z")

</div>

Hi,

Every time I make a change to my plugin I have to restart WEBrick to see  
the  
change in action. It is time consuming. Is there a clean way to avoid  
this  
restart?

Thanks,  
Peter

---

<div class="post-metadata">

**Author:** ![petermichaux](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/46a35a/32.png) [@petermichaux](https://www.ruby-forum.com/u/petermichaux)\
**Post date:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/avoiding-restarting-webrick-while-developing-acts-as-plugin/47537/2 "2005-11-12T12:49:22Z")

</div>

Hi,

in my humble opinion the cleanest and safest way to avoid restarting  
webrick when developing plugins is to use unit tests to see your  
development changes in action.

Regards,  
Trevor

On 8-Nov-05, at 12:28 PM, Peter M. wrote:

> * * *
> 
> Rails mailing list  
> removed\_email\_address@domain.invalid  
> [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails)

–  
Trevor S.  
[http://somethinglearned.com](http://somethinglearned.com)