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
Edouard CHIN 0d3aec4969 Fix ActiveJob logging when callback chain is halted:
- ### Problem

  ActiveJob will always log "Enqueued MyJob (Job ID) ..." even
  if the job doesn't get enqueued through the adapter.
  Same problem happens when performing a Job, "Performed MyJob (Job ID) ..." will be logged even when job wasn't performed at all.
  This situation can happen either if the callback chain is terminated
  (before_enqueue throwing an `abort`) or if an exception is raised.

  ### Solution

  Check if the callback chain is aborted/exception is raised, and  log accordingly.
2019-12-09 16:17:55 +01:00
.github Easy to show bundle exec rubocop output at Action 2019-11-27 00:17:34 +00:00
actioncable Fixup CHANGELOGs [ci skip] 2019-11-24 09:20:00 +09:00
actionmailbox Track Active Storage variants in the database 2019-12-06 13:26:51 -05:00
actionmailer Fixup CHANGELOGs [ci skip] 2019-11-24 09:20:00 +09:00
actionpack Fix Rubocop violation 2019-12-09 12:14:24 -03:00
actiontext Track Active Storage variants in the database 2019-12-06 13:26:51 -05:00
actionview Revert "Merge pull request #37504 from utilum/no_implicit_conversion_of_nil" 2019-12-09 11:50:39 -03:00
activejob Fix ActiveJob logging when callback chain is halted: 2019-12-09 16:17:55 +01:00
activemodel Revert "Merge pull request #37504 from utilum/no_implicit_conversion_of_nil" 2019-12-09 11:50:39 -03:00
activerecord Revert "Merge pull request #37504 from utilum/no_implicit_conversion_of_nil" 2019-12-09 11:50:39 -03:00
activestorage Make sure variant is created on the same service 2019-12-06 22:02:07 -05:00
activesupport Update docs of String methods using ActiveSupport::Inflector [ci skip] (#37890) 2019-12-07 12:11:15 +09:00
ci
guides Update documentation for setting up database tests (#37475) 2019-12-08 11:06:35 +09:00
railties Add CHANGELOG entry for 4d858b3f2a 2019-12-09 15:20:27 +09:00
tasks Fix release task 2019-11-27 12:24:31 -03:00
tools Enable Layout/EmptyLinesAroundAccessModifier cop 2019-06-13 12:00:45 +09:00
.gitattributes
.gitignore Output junit format test report 2019-04-04 14:34:46 +09:00
.rubocop.yml Bump RuboCop version to 0.77 2019-11-27 23:58:49 +00:00
.travis.yml
.yardopts
.yarnrc
Brewfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gemfile Update to listen 3.2 2019-11-24 15:19:54 +01:00
Gemfile.lock Merge pull request #37896 from tgxworld/upgrade_listen 2019-12-06 09:49:54 +09:00
MIT-LICENSE
package.json
rails.gemspec Add Rails changelog URI 2019-11-28 07:57:37 +11:00
RAILS_VERSION Start Rails 6.1 development 2019-04-24 15:57:14 -04:00
Rakefile
README.md unlinks Ruby on Rails Tutorial [skip ci] 2019-12-06 11:26:24 +01:00
RELEASING_RAILS.md update https urls [ci skip] 2019-10-03 11:01:32 +02:00
version.rb Start Rails 6.1 development 2019-04-24 15:57:14 -04:00
yarn.lock Fix outdated yarn.lock 2019-04-25 14:27:11 +05:30

Welcome to Rails

What's 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: Model, View, and Controller, each with a specific responsibility.

Model layer

The Model layer represents the domain model (such as Account, Product, Person, Post, etc.) and encapsulates the business logic 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. 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.

Controller layer

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.

View layer

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.

Frameworks and libraries

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, a library to generate and send emails; Action Mailbox, a library to receive emails within a Rails application; Active Job, a framework for declaring jobs and making them run on a variety of queuing backends; Action Cable, a framework to integrate WebSockets with a Rails application; Active Storage, a library to attach cloud and local files to Rails applications; Action Text, a library to handle rich text content; and Active Support, 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. 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

Code Triage Badge

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!

Trying to report a possible security vulnerability in Rails? Please check out our security policy 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.

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.