Skip to content
This repository

Ruby on Rails

tag: v3.2.7
Octocat-spinner-32 actionmailer updating release date July 26, 2012
Octocat-spinner-32 actionpack updating release date July 26, 2012
Octocat-spinner-32 activemodel updating release date July 26, 2012
Octocat-spinner-32 activerecord updating release date July 26, 2012
Octocat-spinner-32 activeresource updating release date July 26, 2012
Octocat-spinner-32 activesupport updating release date July 26, 2012
Octocat-spinner-32 ci fixed a typo in a message when there is no failuresin a build November 28, 2011
Octocat-spinner-32 railties updating release date July 26, 2012
Octocat-spinner-32 tasks rake release should push the tag November 14, 2011
Octocat-spinner-32 tools Support an extra profile printer arg June 24, 2010
Octocat-spinner-32 .gitignore allow people to set a local .Gemfile so that things like ruby-debug a… November 17, 2011
Octocat-spinner-32 .travis.yml Don't notify campfire when the build keeps passing December 18, 2011
Octocat-spinner-32 .yardopts Let YARD document the railties gem September 09, 2010
Octocat-spinner-32 Gemfile Bumping mocha! July 19, 2012
Octocat-spinner-32 RAILS_VERSION bumping to 3.2.7 July 26, 2012
Octocat-spinner-32 README.rdoc Add dependency status (a la build status) to the README December 08, 2011
Octocat-spinner-32 RELEASING_RAILS.rdoc updates the host and port of publish_docs, and changes the release in… December 08, 2011
Octocat-spinner-32 Rakefile Merge pull request #4278 from kennyj/fix_rdoc_generating_problem January 03, 2012
Octocat-spinner-32 install.rb Add install script for testing gems locally July 26, 2010
Octocat-spinner-32 load_paths.rb This fixes an issue when bundling to a local path (eg. /vendor/bundle). July 18, 2011
Octocat-spinner-32 rails.gemspec Just provide the executable for railtie. This should be fine since Ru… September 12, 2011
Octocat-spinner-32 version.rb bumping to 3.2.7 July 26, 2012
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.

Something went wrong with that request. Please try again.