1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Ruby on Rails
Find a file
Jeremy Daer e35b98e6f5
Action Mailer: Declarative exception handling with rescue_from.
Follows the same pattern as controllers and jobs. Exceptions raised in
delivery jobs (enqueued by `#deliver_later`) are also delegated to the
mailer's rescue_from handlers, so you can handle the DeserializationError
raised by delivery jobs:

```ruby
class MyMailer < ApplicationMailer
  rescue_from ActiveJob::DeserializationError do
    …
  end
```

ActiveSupport::Rescuable polish:
* Add the `rescue_with_handler` class method so exceptions may be
  handled at the class level without requiring an instance.
* Rationalize `exception.cause` handling. If no handler matches the
  exception, fall back to the handler that matches its cause.
* Handle exceptions raised elsewhere. Pass `object: …` to execute
  the `rescue_from` handler (e.g. a method call or a block to
  instance_exec) against a different object. Defaults to `self`.
2016-05-15 18:44:16 -07:00
.github fix typo in pull_request_template [ci skip] 2016-02-26 16:40:42 +09:00
actioncable Merge branch 'master' of github.com:rails/docrails 2016-05-14 09:54:23 +00:00
actionmailer Action Mailer: Declarative exception handling with rescue_from. 2016-05-15 18:44:16 -07:00
actionpack Action Mailer: Declarative exception handling with rescue_from. 2016-05-15 18:44:16 -07:00
actionview Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
activejob Action Mailer: Declarative exception handling with rescue_from. 2016-05-15 18:44:16 -07:00
activemodel Merge branch 'master' of github.com:rails/docrails 2016-05-14 09:54:23 +00:00
activerecord Merge branch 'master' of github.com:rails/docrails 2016-05-14 09:54:23 +00:00
activesupport Action Mailer: Declarative exception handling with rescue_from. 2016-05-15 18:44:16 -07:00
ci Fix some typos in comments. 2016-05-04 12:22:23 -04:00
guides Merge pull request #25002 from maclover7/jm-add-actioncable-guide 2016-05-14 14:57:41 -07:00
railties reorder env keys in the generated config/cable.yml 2016-05-15 00:17:35 +02:00
tasks Publish Action Cable to NPM when we release. 2016-05-11 19:36:27 -07:00
tools Remove requiring load_paths from tools/test.rb 2016-03-02 10:28:34 +05:30
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.travis.yml Run Active Support tests when preserving timezones 2016-05-05 05:07:58 +01:00
.yardopts
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Add notes on cosmetic patches 2016-05-13 15:03:50 -04:00
Gemfile Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
Gemfile.lock Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
rails.gemspec revises the homepage URL in the gemspecs [ci skip] 2016-03-10 07:55:27 +01:00
RAILS_VERSION Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
Rakefile Cable: add isolated tests and FAYE=1 test runs 2016-03-20 17:00:46 -07:00
README.md Fix title of README according to Markdown conventions 2016-02-25 03:39:02 +01:00
RELEASING_RAILS.md Publish Action Cable to NPM when we release. 2016-05-11 19:36:27 -07:00
version.rb Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00

Welcome to Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Understanding the MVC pattern is key to understanding Rails. MVC divides your application into three layers, each with a specific responsibility.

The Model layer represents your domain model (such as Account, Product, Person, Post, etc.) and encapsulates the business logic that is specific to your application. In Rails, database-backed model classes are derived from ActiveRecord::Base. Active Record allows you to present the data from database rows as objects and embellish these data objects with business logic methods. You can read more about Active Record in its README. Although most Rails models are backed by a database, models can also be ordinary Ruby classes, or Ruby classes that implement a set of interfaces as provided by the Active Model module. You can read more about Active Model in its README.

The Controller layer is responsible for handling incoming HTTP requests and providing a suitable response. Usually this means returning HTML, but Rails controllers can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers load and manipulate models, and render view templates in order to generate the appropriate HTTP response. In Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and 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 README.

The View layer is composed of "templates" that are responsible for providing appropriate representations of your application's resources. Templates can 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.

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), a library to generate and send emails; Active Job (README), a framework for declaring jobs and making them run on a variety of queueing backends; Action Cable (README), a framework to integrate WebSockets with a Rails application; and Active Support (README), a collection of utility classes and standard library extensions that are useful for Rails, and may also be used independently outside Rails.

Getting Started

  1. Install Rails at the command prompt if you haven't yet:

     $ gem install rails
    
  2. At the command prompt, create a new Rails application:

     $ rails new myapp
    

    where "myapp" is the application name.

  3. Change directory to myapp and start the web server:

     $ cd myapp
     $ rails server
    

    Run with --help or -h for options.

  4. Using a browser, go to http://localhost:3000 and you'll see: "Yay! Youre on Rails!"

  5. Follow the guidelines to start developing your application. You may find the following resources handy:

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Ruby on Rails guide for guidelines about how to proceed. Join us!

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.

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.