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
Andrew White 9b84567fd4 Check whether Rails.application defined before calling it
In #27674 we changed the migration generator to generate migrations at
the path defined in `Rails.application.config.paths` however the code
checked for the presence of the `Rails` constant but not the
`Rails.application` method which caused problems when using Active
Record and generators outside of the context of a Rails application.

Fixes #28325.
2017-03-07 10:20:21 +00:00
.github Add a note about adding CHANGELOG entries at the top of the file [ci skip] 2016-07-02 22:31:09 +05:30
actioncable Update package.json 2017-02-23 15:03:20 -05:00
actionmailer Deprecate implicit coercion of ActiveSupport::Duration 2017-03-02 08:00:22 +00:00
actionpack Add CHANGELOG entry for #28250 2017-03-06 12:22:21 +00:00
actionview Deprecate implicit coercion of ActiveSupport::Duration 2017-03-02 08:00:22 +00:00
activejob Merge pull request #28112 from bolek/include-job_id-in-all-active-job-logs 2017-02-23 16:18:01 -05:00
activemodel Merge pull request #25296 from kamipo/use_inspect_for_type_cast_for_schema 2017-02-28 18:19:33 -05:00
activerecord Check whether Rails.application defined before calling it 2017-03-07 10:20:21 +00:00
activesupport Fix typo titlelize -> titleize [ci skip] 2017-03-07 08:08:19 +09:00
ci Test rails-ujs in our travis matrix 2017-02-22 13:49:28 -05:00
guides Remove :on option that does ot exist [ci skip] 2017-03-07 15:40:52 +09:00
railties [ci skip] 🎬 expensive: take two 2017-03-06 20:27:00 +01:00
tasks Use shasum 256 on the release 2017-02-24 20:02:37 -05: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 CI against jruby-9.1.8.0 2017-03-07 11:51:23 +09: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 Make security policy more prominent in docs 2017-02-23 18:36:21 -05:00
Gemfile Use released arel 2017-02-21 11:46:42 -05:00
Gemfile.lock Preparing for 5.1.0.beta1 release 2017-02-23 14:53:21 -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 Preparing for 5.1.0.beta1 release 2017-02-23 14:53:21 -05:00
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 Update RELEASING_RAILS.md for rails-ujs 2016-11-26 10:51:44 -05:00
version.rb Preparing for 5.1.0.beta1 release 2017-02-23 14:53:21 -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!

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.