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
Daniel Colson f976dec24b
Add note to avoid requiring config/initializers
[ci skip]

Closes #40021

I began this commit by adding an additional note about explicitly
requiring initializers. `config/intializers` are loaded with `load`
rather than `require` (and always have been, since they were introduced
way back in c6d6082562). So explicitly requiring them can be problematic
if they are not idempotent.

But @p8 pointed out that it is a bit awkward to have 3 notes and one tip
larger than the actual text in this section.

This commit now also reworks 2 of the notes and the tip into additional
paragraphs in the main text. The benefits of the new version I see:

- We now explicitly say that the initializers are loaded by sort order
- We now start with the ideal way to deal with dependent initializers,
  then follow with a couple warnings. We used to lead with what not to
  do, which I think was a bit confusing.
- The language around subdirectories is much simpler (mentioning that
  subdirectories can be used for organizing seemed unnecessary to me -
  that is true of subdirectories in general, and doesn't have any
  specific connection to initializers)

This commit does not change the opening paragraph or the note about when
to use `after_initialize` instead, although it does reformat them.
2020-08-25 20:25:46 -04:00
.github Don't mark issues on a milestone as stale 2020-05-29 10:54:17 +01:00
actioncable Merge pull request #39123 from tannakartikey/actioncable_logger_docs 2020-07-06 14:28:43 -04:00
actionmailbox Sendgrid: prepend X-Original-To header with envelope recipients 2020-07-21 19:38:38 -04:00
actionmailer Merge pull request #26445 from dracos/multiparty 2020-08-19 10:10:36 -07:00
actionpack Allow a proc to be used in addition to a static value for cookies_same_site_protection 2020-08-25 14:33:48 -04:00
actiontext Remove white list word 2020-06-09 13:41:51 -04:00
actionview Allow callers to remove nopush 2020-08-23 09:53:42 -04:00
activejob fix typo in Active Job exceptions docs 2020-07-18 11:05:35 +01:00
activemodel Documents other_than option also accepts the proc or a symbol for numericality validation [skip ci] 2020-08-24 21:27:45 +05:30
activerecord Merge pull request #40104 from p8/happy-human 2020-08-25 22:32:18 +01:00
activestorage Update service metadata for updated Blobs only 2020-08-13 10:45:46 -04:00
activesupport Corrects the config object class [ci skip] 2020-08-23 00:53:22 +05:30
ci
guides Add note to avoid requiring config/initializers 2020-08-25 20:25:46 -04:00
railties Allow a proc to be used in addition to a static value for cookies_same_site_protection 2020-08-25 14:33:48 -04:00
tasks
tools Introduce Rails::TestUnitReporter.app_root to inject app_root when needed. 2020-06-14 00:02:49 +02:00
.gitattributes
.gitignore
.rubocop.yml Remove redundant Exclude in .rubocop.yml 2020-06-29 16:06:48 -07:00
.yardopts
.yarnrc
Brewfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gemfile Use Rouge for guides code highlighting [ci skip] 2020-07-08 09:05:08 +02:00
Gemfile.lock Update Gemfile.lock 2020-08-18 18:14:00 +09:00
MIT-LICENSE
package.json
rails.gemspec Update outdated bundler in gemspec 2020-08-18 00:39:54 +08:00
RAILS_VERSION
Rakefile
README.md
RELEASING_RAILS.md fix: Update Agile Web Development with Rails book link [ci skip] 2020-08-13 10:36:46 +05:30
version.rb
yarn.lock

Welcome to Rails

What's 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: Model, View, and Controller, each with a specific responsibility.

Model layer

The Model layer represents the domain model (such as Account, Product, Person, Post, etc.) and encapsulates the business logic 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. 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.

Controller layer

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.

View layer

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.

Frameworks and libraries

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, a library to generate and send emails; Action Mailbox, a library to receive emails within a Rails application; Active Job, a framework for declaring jobs and making them run on a variety of queuing backends; Action Cable, a framework to integrate WebSockets with a Rails application; Active Storage, a library to attach cloud and local files to Rails applications; Action Text, a library to handle rich text content; and Active Support, 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
     $ bin/rails server
    

    Run with --help or -h for options.

  4. 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.