1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Ruby on Rails
Find a file
2011-10-25 17:44:17 -07:00
actionmailer Correct ActionMailer subject i18n lookup scope. 2011-10-20 12:32:11 +02:00
actionpack properly handle lists of lists. Thanks @adrianpike for reporting! 2011-10-25 17:44:17 -07:00
activemodel Merge branch 'master' of github.com:lifo/docrails 2011-10-20 23:20:44 +05:30
activerecord Merge branch 'master' of github.com:rails/rails 2011-10-25 17:22:55 -05:00
activeresource Merge branch 'master' of github.com:lifo/docrails 2011-10-14 22:21:40 +05:30
activesupport Revert "Merge pull request #3395 from bdurand/fix_file_store_cleanup" 2011-10-25 22:23:25 +02:00
ci Remove cruise files 2011-08-13 16:22:18 -07:00
railties Merge pull request #3357 from rahul100885/rahul100885_ws 2011-10-25 13:43:47 -07:00
tasks Make rails gem build directory consistent with actionpack, etc. 2011-08-04 17:32:43 -04:00
tools
.gitignore Clean up .gitignore and make a note about using global ignores 2011-10-25 13:30:50 -07:00
.travis.yml Don't notify IRC on every single build, just failures and first success after a string of failures 2011-10-08 11:13:48 -07:00
.yardopts
Gemfile No need to check ruby version here 2011-10-22 22:29:38 +05:30
install.rb
load_paths.rb
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
RAILS_VERSION
Rakefile Use Travis https build status image in order to prevent GitHub from 2011-09-08 01:27:24 +05:30
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
version.rb

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