Ruby on Rails
Go to file
Hartley McGuire 7d116c93cf
Convert rails-ujs to ES2015 modules
Building and linting are setup similar to other packages

Most of the changes are related to converting from sprockets requires to
ESM imports/export. However, there are a few notable changes as well:

- A few methods have been refactored to store the Rails object in a
  closure so that properties on it can be overriden by applications (as
  documented and tested). This also resulted in the "start" module
  getting inlined so that it can use the resulting functions.

- The logic for running Rails.start() automatically had to change
  because Rollup uses a slightly different module format than the
  previous coffeescript bundle. The Rollup bundle does not set
  window.Rails until the end up the bundle, so the condition had to be
  updated and window.Rails had to be set manually to ensure backwards
  compatability with scripts listening to the rails:attachBindings event
2022-07-07 21:52:08 -04:00
.devcontainer Fix building docker container 2022-06-22 18:46:29 +09:00
.github Bump ruby version for Rubocop 2022-06-23 08:25:43 -04:00
actioncable Anchor the Action Cable server's route 2022-06-29 13:26:49 -05:00
actionmailbox Improve mailbox generator usage docs 2022-06-21 00:30:49 -05:00
actionmailer Improve mailer generator usage docs 2022-06-21 00:30:27 -05:00
actionpack Ensure Rails is green with Rack-Test main branch 2022-07-06 14:54:01 +02:00
actiontext Omit workers and preload_app! from Puma config 2022-06-03 12:38:21 -05:00
actionview Convert rails-ujs to ES2015 modules 2022-07-07 21:52:08 -04:00
activejob Add `--parent` option to job generator to specify parent class of job. 2022-07-05 20:55:38 -04:00
activemodel Fix code cache namespacing for proxied attribute methods 2022-06-25 09:02:41 +02:00
activerecord Merge pull request #45536 from byroot/foreign-key-flaky-test 2022-07-06 16:16:08 +02:00
activestorage Require ruby-vips before downloading blob 2022-06-23 12:50:08 -05:00
activesupport Clear cache in MemCacheStore tests 2022-07-07 00:25:15 +03:00
ci ✂️ 2021-10-14 16:36:56 +00:00
guides Add documentation to customize full_messages on ActiveModel and ActiveRecord 2022-07-07 13:28:56 -05:00
railties Convert rails-ujs to ES2015 modules 2022-07-07 21:52:08 -04:00
tasks Update the npm package release task to not add the latest package for every version. 2022-06-28 23:16:09 +02:00
tools Replace webpack with importmapped Hotwire as default js (#42999) 2021-08-26 10:39:36 +02:00
.gitattributes
.gitignore Rotate the debug.log on each 100MB 2022-04-13 15:38:19 +03:00
.rubocop.yml Enable `Style/MapToHash` cop 2022-02-26 04:31:03 +09:00
.yardopts Updating .yardopts to document .rb files in [GEM]/app 2019-08-20 13:25:36 -04:00
.yarnrc Make Webpacker the default JavaScript compiler for Rails 6 (#33079) 2018-09-30 22:31:21 -07:00
Brewfile Add libvips to Development Dependency guide 2022-05-01 03:07:21 -04:00
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md 2022-01-18 11:22:46 -05:00
CONTRIBUTING.md Fix 404 links on https://rubyonrails.org/ [ci-skip] 2021-12-17 02:26:34 +09:00
Gemfile Allow rack-test >= 2 2022-07-06 14:54:39 +02:00
Gemfile.lock Allow rack-test >= 2 2022-07-06 14:54:39 +02:00
MIT-LICENSE Bump license years to 2022 [ci-skip] 2022-01-01 15:22:15 +09:00
RAILS_VERSION Start Rails 7.1 development 2021-12-07 15:52:30 +00:00
README.md Convert lib and frameworks to bulleted list-README 2022-02-14 23:15:16 +05:30
RELEASING_RAILS.md Upgrade Release guide to match current practices 2022-05-18 23:04:29 +00:00
Rakefile Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
codespell.txt Fix misspelling of value is tests 2022-02-15 14:50:33 +01:00
package.json Install JavaScript packages before run test 2019-02-11 09:58:08 +09:00
rails.gemspec Fix gemspec 2021-11-15 21:06:21 +00:00
version.rb Fix #version docs and some typos 2022-03-16 01:48:37 +05:30
yarn.lock Convert rails-ujs to ES2015 modules 2022-07-07 21:52:08 -04:00

README.md

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.