Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Ruby on Rails
Ruby CSS Other
branch: rf-experiment-…

This branch is 3 commits ahead, 8229 commits behind master

Merge pull request #15115 from zzak/guides_method_visibility

Document method visibility for designing API docs.
latest commit 8f1244ca15
@chancancode chancancode authored
Failed to load latest commit information.
actionmailer Merge pull request #15083 from zuhao/refactor_actionmailer_i18n_with_…
actionpack _recall should be set to a hash or not set
actionview Be explicit about the API visibility of the methods
activemodel Add singular and plural form for some validation messages
activerecord Fix inheritance of stored_attributes (fixes #14672)
activesupport remove deprecation warning
ci Revert "Merge pull request #14940 from arunagw/hbakhtiyor-test-db-nam…
guides Document method visibility for designing API docs. [ci skip]
railties Ok. Enough models for today :rage:
tasks Fix release task
tools Removing Gem.source_index [ci skip]
.gitignore Updated link to to GitHub article about ignoring files [ci skip]
.travis.yml Test with ruby-head to make @tenderlove happy
.yardopts Let YARD document the railties gem Add info about contributing to docs to
Gemfile Guides: output valid HTML5
RAILS_VERSION update version to 4.2.0.alpha Use SVG version of travis build status badge [skip ci]
RELEASING_RAILS.rdoc Changed 'so' to 'see'
Rakefile Fix task comment to match which file should be changed
install.rb actionview should be able to install using install.rb [ci skip]
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3
rails.gemspec Make possible to use sprockets-rails 2.1
version.rb Introduce `Rails.gem_version`

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. 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 Record 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, 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; 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!

Code Status

  • Build Status


Ruby on Rails is released under the MIT License.

Something went wrong with that request. Please try again.