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
Prathamesh Sonpatki 07563036b0
Move the options for deliver_later up near to the example [ci skip]
- And move the Active Job related section down. Otherwise it was
  appearing as if the options are available for the `delivery_job`
  setting.
2018-01-04 21:51:30 +05:30
.github
actioncable Bump license years for 2018 2017-12-31 22:36:55 +09:00
actionmailer Move the options for deliver_later up near to the example [ci skip] 2018-01-04 21:51:30 +05:30
actionpack Merge pull request #31594 from yuki24/refactor-request-test 2018-01-04 08:23:25 -05:00
actionview Revert unintentional change in 41e3bbd 2018-01-01 13:24:51 -05:00
activejob Bump license years for 2018 2017-12-31 22:36:55 +09:00
activemodel Merge pull request #29018 from willbryant/missing_attributes_after_save 2018-01-03 05:14:18 +09:00
activerecord Partial revert the changing default value of readonly_value 2018-01-05 00:53:47 +09:00
activestorage Configure previewer/analyzer command paths centrally 2018-01-03 22:01:31 -05:00
activesupport Merge pull request #31049 from gwincr11/cg-blank 2018-01-04 23:22:21 +09:00
ci Fix typos and add a few suggestions 2017-11-28 19:27:43 +01:00
guides Move config.action_view.cache_template_loading to proper section in configuring.md [ci skip] 2018-01-03 19:53:51 +02:00
railties Bump license years for 2018 2017-12-31 22:36:55 +09:00
tasks Remove unused variable gem_version from tasks/release.rb 2017-09-24 22:53:10 +03:00
tools
.codeclimate.yml Keep current Code Climate behavior before upgrade 2017-11-29 23:16:04 -05:00
.gitattributes
.gitignore Ignore activestorage/test/service/configurations.yml 2017-09-11 18:03:27 -04:00
.rubocop.yml Enable Layout/LeadingCommentSpace to not allow cosmetic changes in the future 2017-12-14 17:30:54 +09:00
.travis.yml CI against ruby 2.5.0 2017-12-27 10:42:46 +09:00
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gemfile Avoid Minitest 5.11.0 for now 2018-01-02 17:34:09 +09:00
Gemfile.lock Avoid Minitest 5.11.0 for now 2018-01-02 17:34:09 +09:00
MIT-LICENSE Bump license years for 2018 2017-12-31 22:36:55 +09:00
rails.gemspec
RAILS_VERSION Preparing for 5.2.0.beta2 release 2017-11-28 14:41:02 -05:00
Rakefile
README.md
RELEASING_RAILS.md Fix grammar issue [ci skip] 2017-10-31 13:53:37 -04:00
version.rb Preparing for 5.2.0.beta2 release 2017-11-28 14:41:02 -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; Active Storage (README), a library to attach cloud and local files to Rails applications; 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

Code Triage Badge

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.