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
Akira Matsuda 530f7805ed It may be better to explicitly require 'object/try' where we call try
In most cases it works now without explicit require because it's accidentally required through
active_support/core_ext/date_and_time/calculations.rb where we still call `try`,
but that would stop working if we changed the Calculations implementation and remove the require call there.
2019-08-01 18:51:51 +09:00
.github Updated links from http to https in guides, docs, etc 2019-03-09 16:43:47 +05:30
actioncable Use match? where we don't need MatchData 2019-07-29 14:23:10 +09:00
actionmailbox Use try only when we're unsure if the receiver would respond_to the method 2019-08-01 17:58:00 +09:00
actionmailer Do not use the same test class in different tests 2019-08-01 10:26:59 +09:00
actionpack It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
actiontext It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
actionview These methods doesn't have to be protected 2019-08-01 17:58:00 +09:00
activejob Use try only when we're unsure if the receiver would respond_to the method 2019-08-01 17:58:00 +09:00
activemodel It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
activerecord It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
activestorage It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
activesupport It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
ci Use webdrivers instead of chromedriver-helper for AV UJS tests 2019-03-24 16:05:30 -05:00
guides Fix typo in autoload documentation [ci skip] 2019-07-30 12:39:51 -04:00
railties It may be better to explicitly require 'object/try' where we call try 2019-08-01 18:51:51 +09:00
tasks Fix announce script 2019-03-22 00:05:10 -04:00
tools Enable Layout/EmptyLinesAroundAccessModifier cop 2019-06-13 12:00:45 +09:00
.codeclimate.yml Bump rubocop to 0.71 2019-06-06 15:34:50 +05:30
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore Output junit format test report 2019-04-04 14:34:46 +09:00
.rubocop.yml Enable Layout/EmptyLinesAroundAccessModifier cop 2019-06-13 12:00:45 +09:00
.travis.yml Install JavaScript packages before run test 2019-02-11 09:58:08 +09:00
.yardopts
.yarnrc Make Webpacker the default JavaScript compiler for Rails 6 (#33079) 2018-09-30 22:31:21 -07:00
Brewfile [ci skip] Add ImageMagick to Brewfile 2018-08-21 23:01:12 -05:00
CODE_OF_CONDUCT.md Updated links from http to https in guides, docs, etc 2019-03-09 16:43:47 +05:30
CONTRIBUTING.md Updated links from http to https in guides, docs, etc 2019-03-09 16:43:47 +05:30
Gemfile Stop setting a default Capybara app host 2019-07-24 22:19:21 -04:00
Gemfile.lock Stop setting a default Capybara app host 2019-07-24 22:19:21 -04:00
MIT-LICENSE Bump license years for 2019 2018-12-31 10:24:38 +07:00
package.json Install JavaScript packages before run test 2019-02-11 09:58:08 +09:00
rails.gemspec Import Action Text 2019-01-04 22:22:49 -05:00
RAILS_VERSION Start Rails 6.1 development 2019-04-24 15:57:14 -04:00
Rakefile Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
README.md Update README.md 2019-07-30 13:39:14 +06:00
RELEASING_RAILS.md NPM -> npm [ci skip] 2019-05-12 12:00:03 +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.