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 Schuerig mailto:michael-q5aiKMLteq4b1SvskN2V4Q@public.gmane.org http://www.schuerig.de/michael/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---