No, you didn't understand. What I'm telling is, while I'm coding in "development" mode, if I change something in "app/controllers/application_controller.rb", changes appear instantly. But if I change something in "vendor/plugins/ my_plugin/lib/example.rb", I need to restart the server for changes to take effect. (even in "development" mode). In other words, applications files get reloaded on every request, while plugin files load only once and stay in memory. How can I make sure that plugin files also reload with every request?
- thanks On Jul 4, 12:33 am, "Älphä Blüë" <[email protected]> wrote: > Vikrant wrote: > > Hi, > > I have been developing a Rails plugin recently, and I have realised > > that for every change I make into files of my plugin, I have to > > restart the server to make changes take effect. While changes at > > application's own file appear instantly. > > I'm writing only after I searched for an answer over web but didn't > > find any. It's getting irritating now. > > > -thanks > > I think it comes down to what type of plugin you are using first of all. > If the plugin communicates with a database or something that can change > dynamically then it can be done. > > You can specify a configs environment with your plugin for how it > behaves via option types. Load those in a database and have an admin > page that changes the way it works there. I do this with a CMS plugin I > created for my site. > > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
