Rails 5: loading lib files into production

Question

I updated one of my applications from Rails 4.2.6 to Rails 5.0.0. The Update Guide says that Autoload is disabled by default.

Now I always get an error message on my working server, since I load all the autoload lib files into the application.rb file.

 module MyApp class Application < Rails::Application config.autoload_paths += %W( lib/ ) end end 

Currently, I have set config.enable_dependency_loading to true , but I am wondering if there is a better solution for this. There must be a reason Autoloading is shutting down in production by default.

Answer 1

Startup is disabled in the production environment due to thread safety. Thanks @ Green for the link.

I solved this problem by saving the lib files in the lib folder in my app directory, as recommended on Github . Each folder in the app folder is automatically loaded by Rails.

Answer 2

My list of changes after upgrading to Rails 5:

• Put lib dir in the app , because all the code inside the application is automatically loaded into dev and loaded into prod and, most importantly, automatically loaded during development, so you do not need to restart the server every time you make changes.
• Remove all require statements that point to your own classes inside lib , because they all load automatically if the / dir file names are correct, and if you leave require statements, this may break the autoload. More here
• Set config.eager_load = true in all environments to see problems loading the code impatiently in dev.
• Use Rails.application.eager_load! before playing with streams to avoid circular dependency errors.

• If you have ruby ​​/ rails extensions, leave this code in the old lib directory and load them manually from the initializer. This will ensure that the extensions are loaded to your next logic, which may depend on it:

   # config/initializers/extensions.rb Dir["#{Rails.root}/lib/ruby_ext/*.rb"].each { |file| require file } Dir["#{Rails.root}/lib/rails_ext/*.rb"].each { |file| require file } 

Answer 3

There must be a reason why autoload is disabled in the default.

Here is a long discussion on this issue. https://github.com/rails/rails/issues/13142

Answer 4

I just used config.eager_load_paths instead of config.autoload_paths as akostadinov mentioned about github comment: https://github.com/rails/rails/issues/13142#issuecomment-275492070

 # config.autoload_paths << "#{Rails.root}/lib" config.eager_load_paths << "#{Rails.root}/lib" 

He works in a development and production environment.

Answer 5

For those who have struggled with this, just like me, just placing the directory under app/ not enough. Yes, you will get autoload, but not necessarily a reboot, which requires the implementation of naming conventions .

In addition, using the initializer to load the old root lib level will prevent the reboot function during development.

Answer 6

Moving the lib folder to the application helped to solve the problem, my Twitter-avi did not start in production. I had a "uninitialized persistent TwitterApi" and my Twitter API was in my lib folder. I had config.autoload_paths += Dir["#{Rails.root}/app/lib"] in my .rb application, but it did not work before moving the folder.

It did the trick