If you choose to do that, it will
reside in this directory.
??? lib: If you create code that doesn??™t fit neatly into the categories of model or controller,
you can place it in the lib directory. The lib directory is on the load path, but you need
to require the parts you need. Also, when adding new Rake tasks to your build system,
you should put the file containing the tasks in the tasks subdirectory in the lib directory,
so Rake will automatically recognize it.
??? log: When your application is running, all the logs will end up in this directory.
??? public: Some parts of your web application need to be directly accessible without going
through the Rails call stack; for example, images and style sheets. You should put these
things in the public directory. You should also set this directory as the application root
if you??™re using Apache to deploy your application. When caching is configured in your
Rails application, the cached files will end up here too.
??? script: Rails depends on some helper scripts for different purposes. You can find all
of these in this directory. I??™ll describe these scripts further in the section ???Rails Helper
Scripts.???
??? test: You can test Rails applications in many different ways. What is common for all
methods is that you should place the actual tests in this directory. The Rails Rake file
already supports much of the directory structure within, so try to make your testing
fit within the existing architecture.
Pages:
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79