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
Rafael França e4e9d91097 Merge pull request #22709 from jonatack/clarify-explanation-for-new-config-halt-callback-chains
Clarify config settings for AS::halt_callback_chains_on_return_false
2015-12-21 23:32:21 -02:00
actioncable Use the generators options to not generate channel assets 2015-12-21 18:58:08 -02:00
actionmailer No more no changes entries in the CHANGELOGs 2015-12-21 11:46:38 +02:00
actionpack Remember the parameter hash we return 2015-12-22 05:48:38 +10:30
actionview No more no changes entries in the CHANGELOGs 2015-12-21 11:46:38 +02:00
activejob No more no changes entries in the CHANGELOGs 2015-12-21 11:46:38 +02:00
activemodel No more no changes entries in the CHANGELOGs 2015-12-21 11:46:38 +02:00
activerecord Revert "Merge pull request #22486 from methyl/fix-includes-for-groupped-association" 2015-12-21 12:31:52 +01:00
activesupport Use CGI.escapeHTML for html escape 2015-12-21 20:58:42 +09:00
ci Use an appropriate rebuild task on Travis 2015-12-22 00:55:13 +09:00
guides Merge pull request #22709 from jonatack/clarify-explanation-for-new-config-halt-callback-chains 2015-12-21 23:32:21 -02:00
railties Fix Rails tutorial link 2015-12-21 17:25:09 -08:00
tasks Add task to test the release preparation 2015-12-18 14:56:26 -02:00
tools make it possible to customize the executable inside rereun snippets. 2015-06-13 11:58:43 +02:00
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.travis.yml Remove legacy mysql adapter 2015-12-17 15:54:57 +00:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Add specific bug reporting guidelines to contributing.md. [ci skip] 2015-12-15 10:15:24 +01:00
Gemfile Use released rack 2015-12-18 04:54:50 -02:00
Gemfile.lock Change alpha to beta1 to prep for release of Rails 5 2015-12-18 12:14:09 -05:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
rails.gemspec Initial stab at adding Action Cable to rails/master 2015-12-14 16:38:37 +01:00
RAILS_VERSION Change alpha to beta1 to prep for release of Rails 5 2015-12-18 12:14:09 -05:00
Rakefile Add task to test the release preparation 2015-12-18 14:56:26 -02:00
README.md Add Action Cable to README.md of Rails 2015-12-15 09:36:06 -08:00
RELEASING_RAILS.md Convert Releasing Rails guide to Markdown 2015-08-15 09:21:46 -04:00
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.