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
2013-02-25 16:40:35 -05:00
actionmailer Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
actionpack Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
activemodel Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
activerecord removes redundant require 2013-02-25 22:16:30 +01:00
activesupport Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
ci remove duplicate build runs in travis. These extra runs were used to 2012-07-24 16:44:20 -07:00
guides Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
railties Bump sass-rails and coffee-rails to 4.0.0.beta1 in Gemfile 2013-02-25 16:40:35 -05:00
tasks Remove Active Resource source files from the repository 2012-03-13 14:55:44 -04:00
tools Remove REE GC stats since master is 1.9.3 2012-10-26 08:24:27 -07:00
.gitignore Update .gitignore 2013-02-05 14:03:13 -07:00
.travis.yml All green with Ruby 2.0 💚 2013-01-11 02:40:01 -02:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CONTRIBUTING.md add some kindness 2012-09-18 17:57:37 +02:00
Gemfile Bump sass-rails and coffee-rails to 4.0.0.beta1 in Gemfile 2013-02-25 16:40:35 -05:00
install.rb Do not use --local option when installing the gems 2013-02-25 11:51:49 -03:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
rails.gemspec Use sprockets-rails 2.0.0.rc3 in new apps 2013-02-24 13:31:29 -05:00
RAILS_VERSION Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00
Rakefile Pass in --local when doing gem install for local gems. 2013-01-03 15:23:47 +05:30
README.rdoc adding comma to separate clauses 2013-01-21 08:11:39 -08:00
RELEASING_RAILS.rdoc Added extra note about when to email other rubies to RELEASING_RAILS.rdoc 2013-02-01 11:16:28 -08:00
version.rb Preparing for 4.0.0.beta1 release 2013-02-25 08:31:50 -06:00

== 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> or <tt>-h</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.
* {Getting Started with Rails}[http://guides.rubyonrails.org/getting_started.html].
* {Ruby on Rails Tutorial}[http://ruby.railstutorial.org/ruby-on-rails-tutorial-book].
* {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]!

== Code Status

* {<img src="https://secure.travis-ci.org/rails/rails.png"/>}[http://travis-ci.org/rails/rails]
* {<img src="https://gemnasium.com/rails/rails.png?travis"/>}[https://gemnasium.com/rails/rails]

== License

Ruby on Rails is released under the {MIT License}[http://www.opensource.org/licenses/MIT].