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
2017-05-14 08:37:37 +09:00
.github Limit stale checks to issues 2017-04-01 11:27:26 -05:00
actioncable Cleanup CHANGELOGs [ci skip] 2017-04-30 02:41:44 +09:00
actionmailer Should escape meta characters in regexp 2017-05-07 04:10:00 +09:00
actionpack Merge pull request #29062 from eileencodes/force-encoding-to-original-string-encoding 2017-05-12 14:58:46 -04:00
actionview Should escape meta characters in regexp 2017-05-07 04:10:00 +09:00
activejob Cleanup CHANGELOGs [ci skip] 2017-04-30 02:41:44 +09:00
activemodel fix ActiveModel::Validator#kind code examples [ci skip] 2017-05-02 22:52:01 -04:00
activerecord Use timestamp_attributes_for_update_in_model rather than timestamp_attributes_for_update 2017-05-14 08:37:37 +09:00
activesupport Merge pull request #29034 from peterjm/handle_loops_in_exception_handling 2017-05-11 17:45:03 -07:00
ci Skip isolated test runs on older rubies 2017-03-23 03:51:03 +10:30
guides [ci skip] Mailer fixtures in Testing guide. 2017-05-12 20:13:18 +00:00
railties rake -T should load development env by default, not test 2017-05-10 16:43:27 +03:00
tasks Fix the blog post template header 2017-03-20 14:08:09 -04:00
tools Prevent multiple values being set to run_via 2017-02-18 09:49:57 +09:00
.codeclimate.yml Generators and tests are under the same style rules 2016-07-27 20:26:39 -03:00
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore Test rails-ujs in our travis matrix 2017-02-22 13:49:28 -05:00
.rubocop.yml Add Style/EmptyLinesAroundMethodBody in .rubocop.yml and remove extra empty lines 2017-02-12 20:44:15 +09:00
.travis.yml Avoid rubygems 2.6.12 for now 2017-05-04 23:41:55 +09:30
.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 Make security policy more prominent in docs 2017-02-23 18:36:21 -05:00
Gemfile Allow capybara minor releases 2017-05-05 10:26:59 -05:00
Gemfile.lock Allow capybara minor releases 2017-05-05 10:26:59 -05:00
MIT-LICENSE Bump license years for 2017 2016-12-31 08:34:08 -05:00
rails.gemspec applies new string literal convention in the gemspecs 2016-08-06 19:27:12 +02:00
RAILS_VERSION Start Rails 5.2 development 2017-03-22 10:11:39 +10:30
Rakefile Remove Faye mode 2016-10-01 15:35:59 +09:30
README.md Fix http -> https [ci skip] 2017-02-28 22:51:17 +09:00
RELEASING_RAILS.md Bump from h3 to h2 tag 2017-03-25 12:27:52 -04:00
version.rb Start Rails 5.2 development 2017-03-22 10:11:39 +10:30

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!

Trying to report a possible security vulnerability in Rails? Please check out our security policy for guidelines about how to proceed.

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.