Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Ruby on Rails
Ruby CSS Other
Branch: master
Pull request Compare This branch is 9 commits behind rails:master.

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
actionmailer Merge pull request #21865 from Gaurav2728/test_cases_protected_method…
actionpack Fix mounted engine named routes regression
actionview Merge pull request #21894 from abhishekjain16/refactor_with_dry
activejob Added missing specs for not modifying queues when using AJ test helpers
activemodel use ActiveModel::Naming module instead of Model [ci skip]
activerecord Avoid leaking the first relation we call #first on
activesupport Avoid leaking the first relation we call #first on
ci Add the bug report templates to the Travis CI build
guides Merge pull request #21906 from scottgonzalez/form-helpers
railties Merge pull request #21912 from y-yagi/move_prepare_destination_to_public
tasks Allow release when CHANGELOG is changed
tools make it possible to customize the executable inside rereun snippets.
.gitignore .gitignore: Ignore .ruby-version in any subdir
.travis.yml Added beanstalkd to Travis so ActiveJob integration tests for beansta…
.yardopts Let YARD document the railties gem Move the CoC text to the Rails website Changed 'ask the rubyonrails-talk mailing list.' to 'ask it on the ru…
Gemfile Missed Gemfile change in f849cfe
Gemfile.lock use methods for accessing the cache control headers
RAILS_VERSION Start Rails 5 development :tada: [ci skip] Add `Active Model` to a list of independently used modules. Convert Releasing Rails guide to Markdown
Rakefile Remove activejob integration tests
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3
rails.gemspec Require sprockets-rails >= 2
version.rb Start Rails 5 development :tada:

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 them, 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; 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: "Welcome aboard: You're riding Ruby on Rails!"

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


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


Ruby on Rails is released under the MIT License.

Something went wrong with that request. Please try again.