As I understand it, plugins are not reloaded in Rails with each request in development mode. Which makes sense, as generally you add plugins to your app and it's the app you're developing.
But if you are developing a plugin, you have to restart the server with each change to the plugin which has a significant overhead.
Is there any way to make Rails reload your plugin during development, the way it reloads your models and controllers?
I have been struggling with this for some time, too. None of the solutions work, including the autoload_paths
and autoload_once_paths
tricks. Furthermore, the hack with FileUpdateChecker
and initializers also does not help (the checker triggers properly, but the files are not reloaded). Same for config.reload_plugins = true
...
However, there is a solution. In app/controllers/application_controller.rb
add one line:
require_dependency 'your_file_name_here'
The application controller is reloaded on every request and require_dependency
makes your file to be checked for modifications and reloaded accordingly. It worked for me, Apache 2, Passenger 3 and Rails 3.0.3.
I do this by using the shotgun gem.
gem install shotgun
cd /path/to/rails/app
shotgun
slower response time, but reloading all the rails code, not wasting time to write autoload_paths
Easy way, develop your plugin in a folder inside the "app" folder:
This way, all your plugin classes will be reloaded on each request.
Another possibility is to add the path at your application.rb file:
require File.expand_path('../boot', __FILE__)
require 'rails/all'
Bundler.require(:default, Rails.env) if defined?(Bundler)
module SunspotTutorial
class Application < Rails::Application
config.autoload_paths += %W{ #{config.root}/plugins/your_plugin_name/lib }
#lots of other code
end
end
This way your plugin is going to be reloaded all the time.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With