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
Petrik 94050d7dde Move PermissionsPolicy docs to ActionDispatch::HTTP::PermissionsPolicy [ci-skip]
As most of the PermissionsPolicy is defined in
ActionDispatch::HTTP::PermissionsPolicy, it should include most of the
documentation. ActionController::Metal::PermissionsPolicy should
describe controller overrides.

This PR also makes the documentation more similar to the
ActionDispatch::HTTP::ContentSecurityPolicy documentation.

Note:
The Feature-Policy header has been renamed to Permissions-Policy
in the specification. The Permissions-Policy requires a different
implementation and isn't yet supported by all browsers. To avoid
having to rename this middleware in the future we use the new
name for the middleware but keep the old header name in the
documentation for now.

Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
2022-02-22 21:27:39 +01:00
.devcontainer
.github
actioncable Add Oxford commas [ci-skip] 2022-02-21 11:11:11 -06:00
actionmailbox Replace "overwrite" with "override" [ci-skip] 2022-02-21 11:11:11 -06:00
actionmailer Add Oxford commas [ci-skip] 2022-02-21 11:11:11 -06:00
actionpack Move PermissionsPolicy docs to ActionDispatch::HTTP::PermissionsPolicy [ci-skip] 2022-02-22 21:27:39 +01:00
actiontext Implicitly assert no exception is raised in assert_queries & al 2022-02-19 09:11:14 +01:00
actionview Fix formatting of parameters doc [ci-skip] 2022-02-21 11:11:11 -06:00
activejob Mark up inline code [ci-skip] 2022-02-21 11:11:11 -06:00
activemodel Fix formatting of parameters doc [ci-skip] 2022-02-21 11:11:11 -06:00
activerecord Remove duplicate :key_provider option doc [ci-skip] 2022-02-21 11:11:11 -06:00
activestorage Replace backticks with RDoc markup [ci-skip] 2022-02-21 11:11:11 -06:00
activesupport Warm-up to avoid autoloads interfering with class serial 2022-02-22 21:00:16 +10:30
ci
guides Fix small type in CSP guide [ci-skip] 2022-02-21 22:05:58 +01:00
railties Skip apparently-troublesome test on CI for now 2022-02-22 20:43:05 +10:30
tasks
tools
.gitattributes
.gitignore
.rubocop.yml Enable Lint/EnsureReturn cop 2022-02-05 23:58:07 +00:00
.yardopts
.yarnrc
Brewfile
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md 2022-01-18 11:22:46 -05:00
codespell.txt Fix misspelling of value is tests 2022-02-15 14:50:33 +01:00
CONTRIBUTING.md
Gemfile Upgrade to sdoc 2.3.1 2022-02-14 19:36:22 +01:00
Gemfile.lock Upgrade to sdoc 2.3.1 2022-02-14 19:36:22 +01:00
MIT-LICENSE
package.json
rails.gemspec
RAILS_VERSION
Rakefile
README.md Convert lib and frameworks to bulleted list-README 2022-02-14 23:15:16 +05:30
RELEASING_RAILS.md
version.rb
yarn.lock [ci skip] Added a note about Github Codespaces' warning (#44148) 2022-01-21 09:08:50 -05:00

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.

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.

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.

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
  • 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 the Rails bootscreen with your Rails and Ruby versions.

  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.

License

Ruby on Rails is released under the MIT License.