0
-Rails is a web-application and persistence framework that includes everything
0
-needed to create database-backed web-applications according to the
0
-Model-View-Control pattern of separation. This pattern splits the view (also
0
-called the presentation) into "dumb" templates that are primarily responsible
0
-for inserting pre-built data in between HTML tags. The model contains the
0
-"smart" domain objects (such as Account, Product, Person, Post) that holds all
0
-the business logic and knows how to persist themselves to a database. The
0
-controller handles the incoming requests (such as Save New Account, Update
0
-Product, Show Post) by manipulating the model and directing data to the view.
0
-In Rails, the model is handled by what's called an object-relational mapping
0
-layer entitled Active Record. This layer allows you to present the data from
0
-database rows as objects and embellish these data objects with business logic
0
-methods. You can read more about Active Record in
0
-link:files/vendor/rails/activerecord/README.html.
0
-The controller and view are handled by the Action Pack, which handles both
0
-layers by its two parts: Action View and Action Controller. These two layers
0
-are bundled in a single package due to their heavy interdependence. This is
0
-unlike the relationship between the Active Record and Action Pack that is much
0
-more separate. Each of these packages can be used independently outside of
0
-Rails. You can read more about Action Pack in
0
-link:files/vendor/rails/actionpack/README.html.
0
-1. Run the WEBrick servlet: <tt>ruby script/server</tt> (run with --help for options)
0
- ...or if you have lighttpd installed: <tt>ruby script/lighttpd</tt> (it's faster)
0
-2. Go to http://localhost:3000/ and get "Congratulations, you've put Ruby on Rails!"
0
-3. Follow the guidelines on the "Congratulations, you've put Ruby on Rails!" screen
0
-== Example for Apache conf
0
- DocumentRoot /path/application/public/
0
- ErrorLog /path/application/log/server.log
0
- <Directory /path/application/public/>
0
- Options ExecCGI FollowSymLinks
0
-NOTE: Be sure that CGIs can be executed in that directory as well. So ExecCGI
0
-should be on and ".cgi" should respond. All requests from 127.0.0.1 go
0
-through CGI, so no Apache restart is necessary for changes. All other requests
0
-go through FCGI (or mod_ruby), which requires a restart to show changes.
0
-Have "tail -f" commands running on both the server.log, production.log, and
0
-test.log files. Rails will automatically display debugging and runtime
0
-information to these files. Debugging info will also be shown in the browser
0
-on requests from 127.0.0.1.
0
-Breakpoint support is available through the script/breakpointer client. This
0
-means that you can break out of execution at any point in the code, investigate
0
-and change the model, AND then resume execution! Example:
0
- class WeblogController < ActionController::Base
0
- @posts = Post.find_all
0
- breakpoint "Breaking out from the list"
0
-So the controller will accept the action, run the first line, then present you
0
-with a IRB prompt in the breakpointer window. Here you can do things like:
0
-Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
0
- => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
0
- #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
0
- >> @posts.first.title = "hello from a breakpoint"
0
- => "hello from a breakpoint"
0
-...and even better is that you can examine how your runtime objects actually work:
0
- => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
0
- Display all 152 possibilities? (y or n)
0
-Finally, when you're ready to resume execution, you press CTRL-D
0
-You can interact with the domain model by starting the console through script/console.
0
-Here you'll have all parts of the application configured, just like it is when the
0
-application is running. You can inspect domain models, change values, and save to the
0
-database. Starting the script without arguments will launch it in the development environment.
0
-Passing an argument will specify a different environment, like <tt>console production</tt>.
0
-== Description of contents
0
- Holds all the code that's specific to this particular application.
0
- Holds controllers that should be named like weblog_controller.rb for
0
- automated URL mapping. All controllers should descend from
0
- ActionController::Base.
0
- Holds models that should be named like post.rb.
0
- Most models will descend from ActiveRecord::Base.
0
- Holds the template files for the view that should be named like
0
- weblog/index.rhtml for the WeblogController#index action. All views use eRuby
0
- syntax. This directory can also be used to keep stylesheets, images, and so on
0
- that can be symlinked to public.
0
- Holds view helpers that should be named like weblog_helper.rb.
0
- Configuration files for the Rails environment, the routing map, the database, and other dependencies.
0
- Self-contained mini-applications that can bundle together controllers, models, and views.
0
- Application specific libraries. Basically, any kind of custom code that doesn't
0
- belong under controllers, models, or helpers. This directory is in the load path.
0
- The directory available for the web server. Contains subdirectories for images, stylesheets,
0
- and javascripts. Also contains the dispatchers and the default HTML files.
0
- Helper scripts for automation and generation.
0
- Unit and functional tests along with fixtures.
0
- External libraries that the application depends on. Also includes the plugins subdirectory.
0
- This directory is in the load path.
0
+http://github.com/bousquet/tableau/
0
\ No newline at end of file
) is private.
Comments
No one has commented yet.