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
Jon Moss 5f302eabae Merge pull request #22705 from RochesterinNYC/add-order-explanation-to-first-last-guides
Add clarification about `first` and `last` behavior when using `order` [ci skip]
2016-01-18 10:31:39 -05:00
actioncable Merge pull request #23096 from HayleyCAnderson/ha-action-cable-docs 2016-01-18 09:30:42 -05:00
actionmailer Update copyright notice for 2016 2016-01-01 12:31:53 -05:00
actionpack Pass through AP CHANGELOG [ci skip] 2016-01-18 12:05:23 +05:30
actionview Remove ActionView dependence on ActionPack's Mime implementation 2016-01-17 12:20:52 -05:00
activejob Merge pull request #22487 from joshsoftware/issue_22413 2016-01-01 18:58:42 -03:00
activemodel Refactor tz aware types, add support for PG ranges 2016-01-08 14:11:45 -07:00
activerecord Merge pull request #20005 from kamipo/default_expression_support 2016-01-16 04:18:21 -02:00
activesupport Merge pull request #22278 from poporul/master 2016-01-15 10:32:30 -08:00
ci Use an appropriate rebuild task on Travis 2015-12-22 00:55:13 +09:00
guides Merge pull request #22705 from RochesterinNYC/add-order-explanation-to-first-last-guides 2016-01-18 10:31:39 -05:00
railties Avoid multiple default paths to server.pid file 2016-01-16 16:16:43 +01:00
tasks
tools
.gitignore
.travis.yml Update postgresql version to 9.4 for travis. 2016-01-10 04:31:22 +05:30
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md Typo in Contributing.md documentation 2016-01-06 23:34:41 +00:00
Gemfile Ensure sucker_punch < v2 is installed due to the change in public API 2016-01-02 14:54:15 -05:00
Gemfile.lock Checked in changes to Gemfile.lock on latest master 2016-01-17 19:26:10 +05:30
load_paths.rb
rails.gemspec
RAILS_VERSION Change alpha to beta1 to prep for release of Rails 5 2015-12-18 12:14:09 -05:00
Rakefile
README.md
RELEASING_RAILS.md
version.rb Change alpha to beta1 to prep for release of Rails 5 2015-12-18 12:14:09 -05: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. You can read more about Active Record in its README. 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 Model 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, Active Model, 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; Active Job (README), a framework for declaring jobs and making them run on a variety of queueing backends; Action Cable (README), a framework to integrate WebSockets with a Rails application; 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!

Everyone interacting in Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Rails code of conduct.

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.