Skip to content
Ruby on Rails http://rubyonrails.org
Ruby HTML CSS CoffeeScript E JavaScript
Find file
Latest commit 0e70595 @vipulnsward vipulnsward Merge pull request #23571 from y-yagi/remove_deprecated_render_nothin…
…g_from_guide

remove description of `render :nothing` from guide [ci skip]
Failed to load latest commit information.
actioncable Fix typo [ci skip]
actionmailer Revert "When generating a mailer, you must specify Mailer in the clas…
actionpack speed up string xor operation and reduce object allocations
actionview Add some Action Cable CHANGELOG entries
activejob fix typo in `assert_enqueued_jobs` example [ci skip]
activemodel Add documentation about method to describe how it works [ci skip]
activerecord Add numeric type in the doc [ci skip]
activesupport drop array allocations on `html_safe`
ci Remove commented out code in `ci/travis.rb` [ci skip]
guides remove description of `render :nothing` from guide [ci skip]
railties revert dev:cache to rake task, fixes #23410
tasks Wrangle the asset build into something that sounds more general
tools make it possible to customize the executable inside rereun snippets.
.gitignore .gitignore: Ignore .ruby-version in any subdir
.travis.yml Revert "No need to specify Ruby patch version on Travis CI"
.yardopts Let YARD document the railties gem
CODE_OF_CONDUCT.md Move the CoC text to the Rails website
CONTRIBUTING.md Typo in Contributing.md documentation
Gemfile Update turbolinks-rails for passing railties test
Gemfile.lock Update turbolinks-rails for passing railties test
RAILS_VERSION Preparing for Rails 5.0.0.beta2
README.md Replace old Rails greeting references
RELEASING_RAILS.md hotlink to the source and results for AWDwR tests
Rakefile Add task to test the release preparation
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3
rails.gemspec Initial stab at adding Action Cable to rails/master
version.rb Preparing for Rails 5.0.0.beta2

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 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; 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.