Skip to content
Ruby on Rails
Ruby HTML CSS CoffeeScript E JavaScript
Failed to load latest commit information.
.github fix typo in pull_request_template [ci skip] Feb 26, 2016
actioncable CI: run Action Cable browser tests in Sauce Labs May 25, 2016
actionmailer Remove package:clean task May 24, 2016
actionpack Remove package:clean task May 24, 2016
actionview Remove package:clean task May 24, 2016
activejob Remove package:clean task May 24, 2016
activemodel Remove package:clean task May 24, 2016
activerecord Remove package:clean task May 24, 2016
activesupport Add tests for keyword arg to: for Module#delegate May 25, 2016
ci CI: run Action Cable browser tests in Sauce Labs May 25, 2016
guides autoloading guide: specify autoload paths are set when the app boots … May 26, 2016
railties Merge pull request #25119 from javan/actioncable/blade-build May 24, 2016
tasks Remove package:clean task May 24, 2016
tools Remove requiring load_paths from tools/test.rb Mar 2, 2016
.gitattributes adds .gitattributes to enable Ruby-awareness Mar 16, 2016
.gitignore .gitignore: Ignore .ruby-version in any subdir Sep 7, 2015
.travis.yml CI: run Action Cable browser tests in Sauce Labs May 25, 2016
.yardopts Let YARD document the railties gem Sep 9, 2010
CODE_OF_CONDUCT.md Move the CoC text to the Rails website Aug 21, 2015
CONTRIBUTING.md Add notes on cosmetic patches May 13, 2016
Gemfile CI: run Action Cable browser tests in Sauce Labs May 25, 2016
Gemfile.lock Revert back to a compatible bundler version May 25, 2016
RAILS_VERSION Start Rails 5.1 development :tada: May 10, 2016
README.md Fix title of README according to Markdown conventions Feb 25, 2016
RELEASING_RAILS.md Publish Action Cable to NPM when we release. May 11, 2016
Rakefile Cable: add isolated tests and FAYE=1 test runs Mar 20, 2016
rails.gemspec revises the homepage URL in the gemspecs [ci skip] Mar 10, 2016
version.rb Start Rails 5.1 development :tada: May 10, 2016

README.md

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; 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! You’re on Rails!"

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

Contributing

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

License

Ruby on Rails is released under the MIT License.

Something went wrong with that request. Please try again.