Is it right that there are special moments when you might need to restart Webrick to see your changes?

Question

I heard Kevin Skoglund (lynda.com) say that it is good practice to frequently restart Webrick during development. Although you usually don’t have to restart Webrick to see your changes, does it mean that there are certain points when you might need it? Does anyone know what these circumstances may be? It made me wonder if Webrick looked like peeling.

Answer 1

If you work with Lynda.com tutorials, you work with a much earlier version of Rails, and then with the latest version (2.3.2).

Short answer: when working in the development environment, large reboots are no longer required. I think Kevin reboots the server every time you change the Model object, but this is no longer the case.

General rule: restart every time you change something in the config or lib. Folder, any other code changes do not require a restart. It is also recommended that you restart when changing the routes.rb file, although working with it today, I noticed that it is not difficult and fast.

- , - (webrick, mongrel, phusion-) , , Rails , , , , . , , ( , ).

Answer 2

, / .

, Rails Mongrel , .