# Plugin configuration

**URL:** <https://www.ruby-forum.com/t/plugin-configuration/121733>\
**Category:** Rails\
**Created:** [November 30, 2007, 10:39am UTC](https://www.ruby-forum.com/t/plugin-configuration/121733 "2007-11-30T10:39:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wickie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ba9def/32.png) [@wickie](https://www.ruby-forum.com/u/wickie)\
**Post date:** [November 30, 2007, 10:39am UTC](https://www.ruby-forum.com/t/plugin-configuration/121733/1 "2007-11-30T10:39:03Z")

</div>

The common way to supply app specific configuration information for  
plugins appears to be defining constants at the top-level of one of the  
environment files. Even with config/initializers in Rails 2.0 this  
feels a bit clunky. Also, as the application initializers are loaded  
after plugins this might be just too late.

I have no very clear idea of or concrete suggestion for what I’d like to  
have. Maybe a two phase process, where, first, only a config object is  
loaded for a plugin which can be customized in initializers and second  
the plugin proper is loaded with that config. – Or maybe this is just  
overkill for a non-problem.

Michael

–  
Michael S.  
[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
[http://www.schuerig.de/michael/](http://www.schuerig.de/michael/)