Ruby on Rails
Go to file
Santiago Pastorino 18116791d0 Proper lines numbers for stack trace info 2011-09-16 17:28:52 -07:00
actionmailer update 3.1 release date in changelogs 2011-09-14 22:46:12 +05:30
actionpack config.action_controller.asset_host shouldn't set to nil during precompile 2011-09-15 19:55:52 -05:00
activemodel update 3.1 release date in changelogs 2011-09-14 22:46:12 +05:30
activerecord Merge branch 'master' of github.com:lifo/docrails 2011-09-15 00:32:52 +05:30
activeresource update 3.1 release date in changelogs 2011-09-14 22:46:12 +05:30
activesupport Proper lines numbers for stack trace info 2011-09-16 17:28:52 -07:00
ci Remove cruise files 2011-07-26 18:11:03 -03:00
railties config.action_controller.asset_host shouldn't set to nil during precompile 2011-09-15 19:55:52 -05:00
tasks Make rails gem build directory consistent with actionpack, etc. 2011-08-04 17:32:43 -04:00
tools
.gitignore Add .rbenv-version to .gitignore 2011-08-20 15:57:24 -05:00
.travis.yml Update travis config on @joshk's instructions 2011-08-15 17:23:15 +01:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
Gemfile Switching rack-mount to journey. 2011-09-12 16:50:47 -07:00
RAILS_VERSION Master version is 3.2.0.beta 2011-06-30 10:18:36 -03:00
README.rdoc Travis-ci build image should link to the rails travis ci build page rather than to the image. 2011-09-08 22:53:38 -04:00
RELEASING_RAILS.rdoc making the order more clear, adding linux distros mailing lists to our cc 2011-08-16 17:39:58 -07:00
Rakefile Use Travis https build status image in order to prevent GitHub from 2011-09-08 01:27:24 +05:30
install.rb
load_paths.rb This fixes an issue when bundling to a local path (eg. /vendor/bundle). 2011-07-17 15:21:19 +02:00
rails.gemspec Just provide the executable for railtie. This should be fine since Rubygems now warns before overriding them. 2011-09-12 09:05:11 -07:00
version.rb Master version is 3.2.0.beta 2011-06-30 10:18:36 -03:00

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)}[http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller] 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}[link:/rails/rails/blob/master/activerecord/README.rdoc].

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}[link:/rails/rails/blob/master/actionpack/README.rdoc].

== 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 <tt>--help</tt> for options.

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

* The README file created within your application.
* The {Getting Started with Rails}[http://guides.rubyonrails.org/getting_started.html].
* The {Ruby on Rails Tutorial}[http://railstutorial.org/book].
* The {Ruby on Rails Guides}[http://guides.rubyonrails.org].
* The {API Documentation}[http://api.rubyonrails.org].

== Contributing

We encourage you to contribute to Ruby on Rails! Please check out the {Contributing to Rails
guide}[http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html] for guidelines about how
to proceed. {Join us}[http://contributors.rubyonrails.org]!

== Travis Build Status {<img src="https://secure.travis-ci.org/rails/rails.png"/>}[http://travis-ci.org/rails/rails]

== License

Ruby on Rails is released under the MIT license.