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
2014-01-24 12:37:24 +05:30
actionmailer e-mail => email, and subject/verb agreement 2014-01-13 11:56:00 -08:00
actionpack add punctuation 2014-01-13 12:15:52 -08:00
actionview Unused class in AV test 2013-12-25 10:33:42 +09:00
activemodel Merge branch 'master' of github.com:lifo/docrails 2013-12-31 22:44:34 +05:30
activerecord Allow "url" sub key in database.yml configuration 2013-12-30 12:21:14 -05:00
activesupport blank? and present? commit to return singletons [Xavier Noria & Pavel Pravosud] 2013-12-28 20:03:38 +01:00
ci Add ActionView to CI 2013-06-20 17:56:00 +02:00
guides easiy => easy 2014-01-24 12:37:24 +05:30
railties rbconfig is not used in these files 2013-12-26 21:18:14 +01:00
tasks Use annotated git tags for release task 2013-12-18 01:00:13 -07:00
tools Removing Gem.source_index [ci skip] 2013-07-13 12:05:52 +02:00
.gitignore Updated link to to GitHub article about ignoring files [ci skip] 2013-05-05 20:33:24 +05:30
.travis.yml Revert "Install bundle gems to the system not to vendor/bundle" 2013-12-30 09:55:28 +01:00
.yardopts
CONTRIBUTING.md Add info about contributing to docs to CONTRIBUTING.md 2013-06-06 17:57:13 +01:00
Gemfile Only build a ConnectionSpecification if required 2013-12-24 10:02:07 +01:00
install.rb actionview should be able to install using install.rb [ci skip] 2013-07-09 00:10:07 +02:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
rails.gemspec Added activemodel as a explicit dependency 2013-10-02 16:40:17 +02:00
RAILS_VERSION Get ready to release 4.1.0.beta1 2013-12-17 16:05:28 -08:00
Rakefile Fix the install task 2013-10-23 19:42:36 -02:00
README.md Clarify that visiting http://localhost:3000 should be done in a browser. 2013-10-29 10:43:30 -04:00
RELEASING_RAILS.rdoc Use annotated git tags for release task 2013-12-18 01:00:13 -07:00
version.rb Its beta1 all around 2013-12-17 16:10:57 -08: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) pattern.

Understanding the MVC pattern is key to understanding Rails. MVC divides your application into three layers, each with a specific responsibility.

The Model layer represents your domain model (such as Account, Product, Person, Post, etc.) 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 Active Model 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 load and manipulate models, and render view templates in order to generate the appropriate HTTP response. In Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and controller classes are derived from ActionController::Base. Action Dispatch and Action Controller are bundled together in Action Pack. You can read more about Action Pack in its README.

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). Views are typically rendered to generate a controller response, or to generate the body of an email. In Rails, View generation is handled by Action View. You can read more about Action View in its README.

Active Record, Action Pack, and Action View can each be used independently outside Rails. In addition to them, Rails also comes with Action Mailer (README), a library to generate and send emails; and Active Support (README), a collection of utility classes and standard library extensions that are useful for Rails, and may also be used independently outside Rails.

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

  4. Using a browser, 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:

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Ruby on Rails guide for guidelines about how to proceed. Join us!

Code Status

  • Build Status
  • Dependencies

License

Ruby on Rails is released under the MIT License.