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
eileencodes 79ce7d9af6
Deprecate spec_name and use name for configurations
I have so. many. regrets. about using `spec_name` for database
configurations and now I'm finally putting this mistake to an end.

Back when I started multi-db work I assumed that eventually
`connection_specification_name` (sometimes called `spec_name`) and
`spec_name` for configurations would one day be the same thing. After
2 years I no longer believe they will ever be the same thing.

This PR deprecates `spec_name` on database configurations in favor of
`name`. It's the same behavior, just a better name, or at least a
less confusing name.

`connection_specification_name` refers to the parent class name (ie
ActiveRecord::Base, AnimalsBase, etc) that holds the connection for it's
models. In some places like ConnectionHandler it shortens this to
`spec_name`, hence the major confusion.

Recently I've been working with some new folks on database stuff and
connection management and realize how confusing it was to explain that
`db_config.spec_name` was not `spec_name` and
`connection_specification_name`. Worse than that one is a symbole while
the other is a class name. This was made even more complicated by the
fact that `ActiveRecord::Base` used `primary` as the
`connection_specification_name` until #38190.

After spending 2 years with connection management I don't believe that
we can ever use the symbols from the database configs as a way to
connect the database without the class name being _somewhere_ because
a db_config does not know who it's owner class is until it's been
connected and a model has no idea what db_config belongs to it until
it's connected. The model is the only way to tie a primary/writer config
to a replica/reader config. This could change in the future but I don't
see value in adding a class name to the db_configs before connection or
telling a model what config belongs to it before connection. That would
probably break a lot of application assumptions. If we do ever end up in
that world, we can use name, because tbh `spec_name` and
`connection_specification_name` were always confusing to me.
2020-02-24 13:27:07 -05:00
.github Use ruby/setup-ruby action to use Ruby 2.7 2020-02-06 18:02:08 -08:00
actioncable update from PR #36222 2020-02-12 13:31:43 -05:00
actionmailbox Replace Mailgun API key with signing key 2020-02-21 11:33:04 -05:00
actionmailer Enable HashTransformKeys and HashTransformValues cops 2020-02-20 22:37:32 +00:00
actionpack Merge pull request #38524 from BKSpurgeon/master 2020-02-22 06:12:39 +00:00
actiontext Correct grammar in setup comment 2020-02-12 13:31:43 -05:00
actionview Update boolean attributes for actionview tag helper 2020-02-24 10:23:30 -05:00
activejob Fix ActiveJob Test adapter not respecting retry attempts: 2020-02-10 17:59:20 -04:00
activemodel Merge pull request #38401 from vinistock/stop_stringifying_during_attribute_assignment 2020-02-13 16:54:35 -05:00
activerecord Deprecate spec_name and use name for configurations 2020-02-24 13:27:07 -05:00
activestorage Fix URL after repo got moved to libvips Github organization 2020-02-13 21:25:36 +01:00
activesupport Merge pull request #37624 2020-02-17 01:32:23 +01:00
ci Remove .travis.yml and ci/travis.rb 2020-01-02 09:27:53 +09:00
guides Adds additional database-specific rake tasks for multi-database users 2020-02-24 12:05:44 -05:00
railties Deprecate spec_name and use name for configurations 2020-02-24 13:27:07 -05:00
tasks Fix release task 2019-11-27 12:24:31 -03:00
tools Enable Layout/EmptyLinesAroundAccessModifier cop 2019-06-13 12:00:45 +09:00
.gitattributes
.gitignore Output junit format test report 2019-04-04 14:34:46 +09:00
.rubocop.yml Enable HashTransformKeys and HashTransformValues cops 2020-02-20 22:37:32 +00: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 Address Error: caskroom/cask was moved. Tap homebrew/cask-cask instead. 2019-12-18 18:50:57 +09:00
CODE_OF_CONDUCT.md Updated links from http to https in guides, docs, etc 2019-03-09 16:43:47 +05:30
CONTRIBUTING.md Updated links from http to https in guides, docs, etc 2019-03-09 16:43:47 +05:30
Gemfile rexml has been bundled gems in Ruby 2.8 (3.0) 2020-01-14 09:35:37 +09:00
Gemfile.lock bumping rubocop to 0.80 2020-02-20 15:08:20 +00:00
MIT-LICENSE Bump license years from 2019 to 2020 [ci skip] 2020-01-01 15:10:31 +05:30
package.json Install JavaScript packages before run test 2019-02-11 09:58:08 +09:00
rails.gemspec Add Rails changelog URI 2019-11-28 07:57:37 +11:00
RAILS_VERSION Start Rails 6.1 development 2019-04-24 15:57:14 -04:00
Rakefile Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
README.md remove reference to global rails command and replace with bin/rails 2019-12-27 19:32:37 +00:00
RELEASING_RAILS.md update https urls [ci skip] 2019-10-03 11:01:32 +02:00
version.rb Start Rails 6.1 development 2019-04-24 15:57:14 -04:00
yarn.lock Fix outdated yarn.lock 2019-04-25 14:27:11 +05:30

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.