This means you can change the validators in your model, and the
next time you hit the browser, the changes will be there, without having to restart the web server or Rails. In
the same way, you can change controllers and views and never have to restart.
CHAPTER 4 ?– STORE ADMINISTRATION 39
Another difference from what you might expect is that caching isn??™t turned on. The error messages are
also informative, and tell things that you should never let a user see. A third thing is that the development
environment enables the breakpoint server automatically. See Chapter 3 for more information about the
breakpointer.
test
The most important thing to remember about the test environment is that you never use it explicitly.Whenever
you run any tests in Rails, the test environment is used, but you shouldn??™t specify it explicitly when
starting a Rails console or web server. To make sure everything is as Rails expects it to be when running
tests, the database in question is always re-created before each test run. So, don??™t store any important data
here.
Information is cached when testing, but error messages are still on the more talkative side.
production
The production environment is where your application should run in production, simply. Caching happens, the
production database is used, and error messages are specifically written for users, not developers.
staging
The staging runtime environment doesn??™t come with Rails. It??™s something that many in the community wish
were there, though.
Pages:
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110