Ruby on Rails + GitHub patches
Ruby CSS
Pull request Compare This branch is 1798 commits ahead, 32183 commits behind rails:master.
Latest commit 4fc14b1 Nov 9, 2014 @charliesome charliesome 3.2.19.github9
Failed to load latest commit information.
actionmailer Remove Proc#bind from Rails 3.2 Oct 8, 2014
actionpack whoops, we don't want to create an output_buffer local Oct 7, 2014
activemodel Merge remote-tracking branch 'upstream/3-2-stable' into 3-2-github Sep 15, 2014
activerecord Move commit exception handling to a method so we can override Sep 26, 2014
activeresource Preparing for 3.2.19 release Jul 2, 2014
activesupport Force a period when local times are ambiguous Nov 10, 2014
ci fixed a typo in a message when there is no failuresin a build Nov 28, 2011
railties move serialization option from cookie option to global env option Sep 23, 2014
script ci on ruby 2.1.2 Sep 15, 2014
tasks rake release should push the tag Nov 14, 2011
tools Support an extra profile printer arg Jun 24, 2010
vendor/cache remove sprockets dependency Sep 15, 2014
.gitignore check in Gemfile.lock because the lack of it is causing problems Apr 10, 2014
.travis.yml Rails 3.2.x is now compatible with Ruby 2.0.0 Feb 24, 2013
.yardopts Let YARD document the railties gem Sep 9, 2010
Gemfile Merge remote-tracking branch 'upstream/3-2-stable' into 3-2-github Sep 15, 2014
Gemfile.lock remove sprockets dependency Sep 15, 2014
RAILS_VERSION 3.2.19.github9 Nov 10, 2014
README.rdoc Add dependency status (a la build status) to the README Dec 8, 2011
RELEASING_RAILS.rdoc updates the host and port of publish_docs, and changes the release in… Dec 8, 2011
Rakefile Merge pull request #4278 from kennyj/fix_rdoc_generating_problem Jan 3, 2012
install.rb Add install script for testing gems locally Jul 26, 2010
load_paths.rb This fixes an issue when bundling to a local path (eg. /vendor/bundle). Jul 17, 2011
rails.gemspec Add license to the gemspec Jul 8, 2013
version.rb Preparing for 3.2.19 release Jul 2, 2014

README.rdoc

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

The Model layer represents your domain model (such as Account, Product, Person, Post) 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 ActiveModel 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 manipulate models and render view templates in order to generate the appropriate HTTP response.

In Rails, the Controller and View layers are handled together by Action Pack. These two layers are bundled in a single package due to their heavy interdependence. This is unlike the relationship between Active Record and Action Pack which are independent. Each of these packages can be used independently outside of Rails. You can read more about Action Pack in its README.

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 for options.

  4. Go to 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 Rails guide for guidelines about how to proceed. Join us!

Build Status

Dependency Status

License

Ruby on Rails is released under the MIT license.