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
Yves Senn 632f4a08a5 doc, hide non-public methods form the api docs. [ci skip]
This is a follow up to #25681, specifically this comment:
https://github.com/rails/rails/pull/25681#issuecomment-238294002

The way the thread local variable is stored is an implementation detail
and subject to change. It makes no sense to only generate a reader or
writer as you'd have to know where to read from or where it writes to.
2016-10-20 21:22:44 +02:00
.github fix typo in pull_request_template [ci skip] 2016-02-26 16:40:42 +09:00
actioncable Permit same-origin connections by default 2016-10-12 10:23:10 +10:30
actionmailer Add load hooks to all tests classes 2016-08-25 04:27:34 -03:00
actionpack Merge pull request #26793 from zachaysan/master 2016-10-15 11:11:39 -03:00
actionview Merge pull request #26578 from jeremy/undeprecate-plural-positional-arg 2016-10-10 02:15:34 -03:00
activejob use descendants to get class that inherited ActiveJob::Base 2016-09-05 17:51:39 +01:00
activemodel Merge pull request #26640 from Shopify/fix-am-errors-to-hash-default-proc 2016-09-27 10:10:48 -03:00
activerecord Revert "Merge pull request #26785 from yahonda/diag26774" 2016-10-16 23:49:28 -03:00
activesupport doc, hide non-public methods form the api docs. [ci skip] 2016-10-20 21:22:44 +02:00
ci Fix some typos in comments. 2016-05-04 12:22:23 -04:00
guides guides, include note about modifiers when using the CLI. 2016-10-20 21:22:36 +02:00
railties Merge pull request #26637 from y-yagi/prevent_plugin_test_run_twice 2016-09-27 16:57:57 +02:00
tasks Fix release task now that NPM is part of the build 2016-08-10 15:33:46 -07:00
tools Remove requiring load_paths from tools/test.rb 2016-03-02 10:28:34 +05:30
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.travis.yml Merge pull request #26800 from prathamesh-sonpatki/bump-bundler 2016-10-16 20:12:27 -03: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 Typo in Contributing.md documentation 2016-01-06 23:34:41 +00:00
Gemfile Only use blade on the 'ruby' platform. 2016-10-19 17:16:24 -05:00
Gemfile.lock Update sqlite3 gem 2016-10-12 18:55:22 -05:00
rails.gemspec revises the homepage URL in the gemspecs [ci skip] 2016-03-10 07:55:27 +01:00
RAILS_VERSION bumping the version 2016-08-10 15:41:59 -07:00
Rakefile Cable: add isolated tests and FAYE=1 test runs 2016-03-20 17:00:46 -07:00
README.md Fix links to source code [ci skip] 2016-07-01 12:46:00 +05:30
RELEASING_RAILS.md Publish Action Cable to NPM when we release. 2016-06-30 15:16:15 -03:00
version.rb bumping the version 2016-08-10 15:41:59 -07: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 that, 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: "Yay! Youre 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.