Go to file
Eugene Kenny fdd76b7370 Clarify that config.eager_load controls eager loading [ci skip]
Before Rails 4.0, `config.cache_classes` determined whether application
code was eager loaded. The `config.eager_load` option was introduced to
allow the two behaviours to be configured independently, but this
documentation was never updated to reflect that change.
2017-12-30 22:37:44 +00:00
.github Limit stale checks to issues 2017-04-01 11:27:26 -05:00
actioncable Preparing for 5.2.0.beta2 release 2017-11-28 14:41:02 -05:00
actionmailer Enable Layout/SpaceBeforeComma rubocop rule, and fixed more 2017-12-12 20:00:50 +09:00
actionpack let drb make temprary server 2017-12-29 23:58:43 +09:00
actionview Remove needless blank lines [ci skip] 2017-12-30 16:58:47 +09:00
activejob Explicitly require sidekiq/cli 2017-12-16 11:02:26 +09:00
activemodel Fix validation callbacks on multiple context 2017-12-20 00:27:19 +09:00
activerecord Fix cache_key with a relation having distinct and order 2017-12-30 18:27:09 +09:00
activestorage prevent shadowing outer variables 2017-12-25 22:47:55 +01:00
activesupport Test that cache stores build unversioned keys 2017-12-22 14:05:12 -05:00
ci Fix typos and add a few suggestions 2017-11-28 19:27:43 +01:00
guides Clarify that config.eager_load controls eager loading [ci skip] 2017-12-30 22:37:44 +00:00
railties Clarify that config.eager_load controls eager loading [ci skip] 2017-12-30 22:37:44 +00:00
tasks Remove unused variable gem_version from tasks/release.rb 2017-09-24 22:53:10 +03:00
tools Use frozen string literal in tools/ 2017-08-13 22:04:59 +09:00
.codeclimate.yml Keep current Code Climate behavior before upgrade 2017-11-29 23:16:04 -05:00
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore Ignore activestorage/test/service/configurations.yml 2017-09-11 18:03:27 -04:00
.rubocop.yml Enable Layout/LeadingCommentSpace to not allow cosmetic changes in the future 2017-12-14 17:30:54 +09:00
.travis.yml CI against ruby 2.5.0 2017-12-27 10:42:46 +09:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Remove html tag making markdown misrender [ci skip] 2017-06-05 22:11:57 -05:00
Gemfile Use released delayed_job instead of master version 2017-12-30 06:57:28 +09:00
Gemfile.lock Use released delayed_job instead of master version 2017-12-30 06:57:28 +09:00
MIT-LICENSE Bump license years for 2017 2016-12-31 08:34:08 -05:00
RAILS_VERSION Preparing for 5.2.0.beta2 release 2017-11-28 14:41:02 -05:00
rails.gemspec Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
Rakefile Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
README.md Update MIT licenses link [ci skip] 2017-08-22 08:46:02 +09:00
RELEASING_RAILS.md Fix grammar issue [ci skip] 2017-10-31 13:53:37 -04:00
version.rb Preparing for 5.2.0.beta2 release 2017-11-28 14:41:02 -05: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; Active Storage (README), a library to attach cloud and local files to Rails applications; 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

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.