I am working on an existing Rail 2.3.x application, so I was working on it and it was very good The message was difficult I was able to run the application. But now for every small change in my controller, I hope that I do not have to start my setter again, otherwise the changes are not being shown back, let's take an example scenario here, let's first get one Say in the filterer method, I have just given a statement at the top of the method and it was not printing in the log, I'm printing it after the restarting the server, what E can tell me that I'm missing something here.
Which environment are you using?
The default environment is 'development', where the code reloads on each request. However, this behavior can be overwritten in the config file.
To ensure that the code has been reloaded, add it to your config / development.rb file:
# In the development environment, your application code # reloads on each request. It reduces response time, but is perfect for development # When you do not need to restart the webserver when you make a code change Config.cache_classes = false 
Comments
Post a Comment