Go to file
Rafael Mendonça França 0cad778c26
Merge branch '4-1-16' into 4-1-stable
2016-07-12 23:48:24 -03:00
actionmailer Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
actionpack Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
actionview Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
activemodel Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
activerecord Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
activesupport Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
ci Add ActionView to CI 2013-06-20 17:56:00 +02:00
guides Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
railties Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
tasks Sign the tag when releasing 2016-06-30 21:52:18 -03:00
tools Removing Gem.source_index [ci skip] 2013-07-13 12:05:52 +02:00
.gitignore Merge pull request #18992 from rails/rm-track-lock-file 2015-02-18 15:57:22 -02:00
.travis.yml Merge pull request #22792 from maclover7/patch-3 2015-12-25 14:54:31 -02:00
.yardopts
CONTRIBUTING.md
Gemfile Make sure we use mime-types 2 to avoid build error with ruby 1.9 2016-06-30 22:42:07 -03:00
Gemfile.lock Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
RAILS_VERSION Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00
README.md updated Travis build status image url 2014-02-14 14:24:52 +01:00
RELEASING_RAILS.rdoc releasing Rails no longer needs triggering docs generation by hand [ci skip] 2014-02-20 23:35:44 +01:00
Rakefile Fix task comment to match which file should be changed 2014-03-25 15:37:08 -03:00
install.rb actionview should be able to install using install.rb [ci skip] 2013-07-09 00:10:07 +02:00
load_paths.rb
rails.gemspec Do not package the guides output 2014-10-31 12:28:16 -02:00
version.rb Preparing for 4.1.16 release 2016-07-12 19:18:54 -03:00

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

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!

Code Status

  • Build Status

License

Ruby on Rails is released under the MIT License.