ruby on rails - Is it correct that there are particular times when you may need to restart Webrick to see your changes? -


I have heard that Kwin Skagland (Linda.com) says that during the development often the habit of restarting Vibriac This is a good practice to come in. Although generally you do not have to restart Webrick to see your changes, they have defined that this time may be required? Does anyone know what those circumstances might be? It is surprising that if Webrick is a type of failure.

If you are working through the Lynda.com tutorial, then you have a lot of rail If you are working with the version then the most recent release (2.3.2).

In short, the restoration in large amounts will not be necessary while working in the environment of development. I think Kevin restarves the server every time you change a model object, but it is not.

The general rule of thumb is: every time you change something in the Config or Lib folder, restart. . . There should be no need to restart any other code changes whenever you change your messages, even then it is a good idea to restart it. Even the RB file, while working with it today, I saw that it is not a tough and fast rule. The reason for restarting all the servers is not required because your webserver (Vibric, Mongel, Fusion passenger) is uneven, but because when your Rail app is started, some things are loaded into memory. , Load Path, Initial, Environmental Data When you change any of these files, you want to restart your application so that changes are made (as opposed to the old stuff that still Running Emori)


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -