The <em>Controller layer</em> is responsible for handling incoming HTTP requests and
providing a suitable response. Usually this means returning \HTML, but \Rails controllers
The Controller layer is responsible for handling incoming HTTP requests and providing a
can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers load and
suitable response. Usually this means returning \HTML, but \Rails controllers can also
manipulate models, and render view templates in order to generate the appropriate HTTP response.
generate XML, JSON, PDFs, mobile-specific views, and more. Controllers manipulate models
In \Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and
and render view templates in order to generate the appropriate HTTP response.
controller classes are derived from ActionController::Base. Action Dispatch and Action Controller
are bundled together in Action Pack. You can read more about Action Pack in its
In \Rails, the Controller and View layers are handled together by Action Pack.
{README}[link:files/actionpack/README_rdoc.html].
These two layers are bundled in a single package due to their heavy interdependence.
This is unlike the relationship between Active Record and Action Pack, which are
The <em>View layer</em> is composed of "templates" that are responsible for providing
independent. Each of these packages can be used independently outside of \Rails. You
appropriate representations of your application's resources. Templates can
can read more about Action Pack in its {README}[link:files/actionpack/README_rdoc.html].
come in a variety of formats, but most view templates are \HTML with embedded
Ruby code (ERB files). Views are typically rendered to generate a controller response,
or to generate the body of an email. In \Rails, View generation is handled by Action View.
You can read more about Action View in its {README}[link:files/actionview/README_rdoc.html].
Active Record, Active Model, Action Pack, and Action View can each be used independently outside \Rails.
In addition to that, \Rails also comes with Action Mailer ({README}[link:files/actionmailer/README_rdoc.html]), a library
to generate and send emails; Active Job ({README}[link:files/activejob/README_md.html]), a
framework for declaring jobs and making them run on a variety of queueing
backends; Action Cable ({README}[link:files/actioncable/README_md.html]), a framework to
integrate WebSockets with a \Rails application;
Active Storage ({README}[link:files/activestorage/README_md.html]), a library to attach cloud
and local files to \Rails applications;
and Active Support ({README}[link:files/activesupport/README_rdoc.html]), a collection
of utility classes and standard library extensions that are useful for \Rails,
and may also be used independently outside \Rails.
== Getting Started
== Getting Started
...
@@ -45,28 +60,31 @@ can read more about Action Pack in its {README}[link:files/actionpack/README_rdo
...
@@ -45,28 +60,31 @@ can read more about Action Pack in its {README}[link:files/actionpack/README_rdo
3. Change directory to +myapp+ and start the web server:
3. Change directory to +myapp+ and start the web server:
$ cd myapp; rails server
$ cd myapp
$ rails server
Run with <tt>--help</tt> or <tt>-h</tt> for options.
Run with <tt>--help</tt> or <tt>-h</tt> for options.
4. Go to http://localhost:3000 and you'll see:
4. Go to <tt>http://localhost:3000</tt> and you'll see: "Yay! You’re on \Rails!"
"Yay! You’re on Rails!"
5. Follow the guidelines to start developing your application. You may find the following resources handy:
5. Follow the guidelines to start developing your application. You may find the following resources handy:
* The \README file created within your application.
* The \README file created within your application.
* {Getting Started with \Rails}[http://guides.rubyonrails.org/getting_started.html].
* {Getting Started with \Rails}[http://guides.rubyonrails.org/getting_started.html].
* {Ruby on \Rails Tutorial}[https://www.railstutorial.org/book].
* {Ruby on \Rails Guides}[http://guides.rubyonrails.org].
* {Ruby on \Rails Guides}[http://guides.rubyonrails.org].
* {The API Documentation}[http://api.rubyonrails.org].
* {The API Documentation}[http://api.rubyonrails.org].
* {Ruby on \Rails Tutorial}[https://www.railstutorial.org/book].
== Contributing
== Contributing
We encourage you to contribute to Ruby on \Rails! Please check out the {Contributing to Rails
We encourage you to contribute to Ruby on \Rails! Please check out the
guide}[http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html] for guidelines about how
{Contributing to Ruby on \Rails guide}[http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html] for guidelines about how to proceed. {Join us!}[http://contributors.rubyonrails.org]
to proceed. {Join us}[http://contributors.rubyonrails.org]!
Trying to report a possible security vulnerability in \Rails? Please
check out our {security policy}[http://rubyonrails.org/security/] for
guidelines about how to proceed.
Everyone interacting in \Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the \Rails {code of conduct}[http://rubyonrails.org/conduct/].