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
2016-05-03 20:49:07 +09:00
.github fix typo in pull_request_template [ci skip] 2016-02-26 16:40:42 +09:00
actioncable [ci skip] Fix ActionCable README 2016-05-02 23:33:12 +09:00
actionmailer Prep Rails 5 beta 4 2016-04-27 15:48:47 -05:00
actionpack Merge pull request #24777 from tomkadwill/action_pack_typos_3 2016-04-30 22:17:12 +05:30
actionview Push action_view.collection_caching to be called towards the end, since it depends on being called after action_controller.set_configs. 2016-04-28 02:51:10 +05:30
activejob Chomp: prefer String#chomp where we can for a clarity boost 2016-04-29 13:43:15 -07:00
activemodel Chomp: prefer String#chomp where we can for a clarity boost 2016-04-29 13:43:15 -07:00
activerecord remove empty? from CHANGELOG [ci skip] 2016-05-03 20:49:07 +09:00
activesupport Fix template resolver cache concurrency: "can't add a new key into hash during iteration" 2016-05-02 15:05:03 -07:00
ci Remove commented out code in ci/travis.rb [ci skip] 2016-02-04 09:15:25 +09:00
guides Replace ActionDispatch::LoadInterlock with ActionDispatch::Executor in guides [ci skip] 2016-04-30 19:39:38 -07:00
railties Prep Rails 5 beta 4 2016-04-27 15:48:47 -05:00
tasks Fix release script to allow pre release gems 2016-04-27 15:48:47 -05: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 CI: allow JRuby build to fail, too flaky to be useful 2016-04-25 19:30:37 -05: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 Merge pull request #23461 from kamipo/prepared_statements_for_mysql2_adapter 2016-04-23 22:28:52 -07:00
Gemfile.lock Fix template resolver cache concurrency: "can't add a new key into hash during iteration" 2016-05-02 15:05:03 -07:00
rails.gemspec revises the homepage URL in the gemspecs [ci skip] 2016-03-10 07:55:27 +01:00
RAILS_VERSION Prep Rails 5 beta 4 2016-04-27 15:48:47 -05:00
Rakefile Cable: add isolated tests and FAYE=1 test runs 2016-03-20 17:00:46 -07:00
README.md Fix title of README according to Markdown conventions 2016-02-25 03:39:02 +01:00
RELEASING_RAILS.md Update to the Rails 5 version of the book 2016-04-27 20:20:12 -04:00
version.rb Prep Rails 5 beta 4 2016-04-27 15:48:47 -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 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.