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
Eugene Kenny 8d3ca97032 Use __id__ to dedup records for transactional callbacks
While not a particularly good idea, it's possible to use `object_id` as
an attribute name, typically by defining a polymorphic association named
`object`. Since 718a32ca74, transactional
callbacks deduplicate records by their `object_id`, but this causes
incorrect behaviour when the record has an attribute with that name.

Using `__id__` instead makes a naming collision much less likely.
2020-04-19 22:48:55 +01:00
.github Add rubocop group to Gemfile for use in CI 2020-03-27 23:55:26 +00:00
actioncable Convert CoffeeScript to ES6 syntax 2020-04-17 14:41:40 +03:00
actionmailbox Add option to set X-Original-To for systems that route on envelope addressing 2020-04-13 15:14:53 -07:00
actionmailer Make _protected_ivars private 2020-04-07 12:45:19 -04:00
actionpack Reduce calls to get path info when finding routes 2020-04-09 21:24:53 -04:00
actiontext Update the Rails mailing list URLs to new discuss discourse URL [ci skip] 2020-04-02 22:00:28 +05:30
actionview Merge pull request #38950 from joelhawksley/annotations-error-line 2020-04-14 18:39:25 -04:00
activejob Merge pull request #38891 from jonathanhefner/fix-activejob-delay-test 2020-04-18 23:55:36 +01:00
activemodel Fixup CHANGELOGs [ci skip] 2020-04-15 21:23:24 +09:00
activerecord Use __id__ to dedup records for transactional callbacks 2020-04-19 22:48:55 +01:00
activestorage Fixup CHANGELOGs [ci skip] 2020-04-15 21:23:24 +09:00
activesupport Fixup CHANGELOGs [ci skip] 2020-04-15 21:23:24 +09:00
ci Remove .travis.yml and ci/travis.rb 2020-01-02 09:27:53 +09:00
guides Add missing backticks [ci skip] 2020-04-19 02:57:43 +05:00
railties Don't gitignore tmp/pids/.keep 2020-04-16 22:51:51 +01:00
tasks Fix release task 2019-11-27 12:24:31 -03:00
tools
.gitattributes
.gitignore
.rubocop.yml Bump rubocop to 0.82 (#38980) 2020-04-17 14:24:33 -04:00
.yardopts Updating .yardopts to document .rb files in [GEM]/app 2019-08-20 13:25:36 -04:00
.yarnrc
Brewfile Address Error: caskroom/cask was moved. Tap homebrew/cask-cask instead. 2019-12-18 18:50:57 +09:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Update the Rails mailing list URLs to new discuss discourse URL [ci skip] 2020-04-02 22:00:28 +05:30
Gemfile Remove more code for unsupported frontbase and ibm_db adapters 2020-04-12 11:45:28 +09:00
Gemfile.lock Bump rubocop to 0.82 (#38980) 2020-04-17 14:24:33 -04:00
MIT-LICENSE Bump license years from 2019 to 2020 [ci skip] 2020-01-01 15:10:31 +05:30
package.json
rails.gemspec Update the Rails mailing list URLs to new discuss discourse URL [ci skip] 2020-04-02 22:00:28 +05:30
RAILS_VERSION
Rakefile
README.md remove reference to global rails command and replace with bin/rails 2019-12-27 19:32:37 +00:00
RELEASING_RAILS.md update https urls [ci skip] 2019-10-03 11:01:32 +02:00
version.rb
yarn.lock chore: updated package.json to include fsevents compatible version for 2020-03-04 11:45: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
     $ bin/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.