kotovalexarian-likes-github/rails--rails

mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00

Ruby on Rails

activejob activerecord framework html mvc rails ruby

Find a file

Sean Griffin 0f1d0b1b52 Consistently apply adapter behavior when serializing arrays In `f1a0fa9` we moved backend specific timestamp behavior out of the type and into the adapter. This was in line with our general attempt to reduce the number of adapter specific type subclasses. However, on PG, the array type performs all serialization, including database encoding in its serialize method. This means that we have converted the value into a string before reaching the database, so no adapter specific logic can be applied (and this also means that timestamp arrays were using the default `.to_s` method on the given object, which likely meant timestamps were being ignored in certain cases as well) Ultimately I want to do a more in depth refactoring which separates database serializer objects from the active model type objects, to give us a less awkward API for introducing the attributes API onto Active Model. However, in the short term, we follow the solution we've applied elsewhere for this. Move behavior off of the type and into the adapter, and use a data object to allow the type to communicate information up the stack. Fixes #27514.		2017-01-03 11:15:16 -05:00
.github
actioncable	Bump license years for 2017	2016-12-31 08:34:08 -05:00
actionmailer	Bump license years for 2017	2016-12-31 08:34:08 -05:00
actionpack	Bump license years for 2017	2016-12-31 08:34:08 -05:00
actionview	Bump license years for 2017	2016-12-31 08:34:08 -05:00
activejob	Merge pull request #27508 from zzz6519003/patch-1	2017-01-01 22:58:50 -05:00
activemodel	Revert "Merge pull request #27528 from kamipo/extract_casted_booleans"	2017-01-01 14:34:04 +01:00
activerecord	Consistently apply adapter behavior when serializing arrays	2017-01-03 11:15:16 -05:00
activesupport	Merge pull request #27520 from prathamesh-sonpatki/merge-uncountable-tests-for-inflector	2017-01-01 15:43:10 -05:00
ci
guides	Update schema cache doc in guides/command_line	2016-12-31 11:42:23 -05:00
railties	Merge pull request #27435 from kamipo/follow_up_25307	2017-01-03 11:19:47 -05:00
tasks
tools
.codeclimate.yml
.gitattributes
.gitignore
.rubocop.yml
.travis.yml
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gemfile
Gemfile.lock
MIT-LICENSE	Bump license years for 2017	2016-12-31 08:34:08 -05:00
rails.gemspec
RAILS_VERSION
Rakefile
README.md
RELEASING_RAILS.md
version.rb

README.md

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

Install Rails at the command prompt if you haven't yet:
```
 $ gem install rails
```
At the command prompt, create a new Rails application:
```
 $ rails new myapp
```
where "myapp" is the application name.
Change directory to myapp and start the web server:
```
 $ cd myapp
 $ rails server
```
Run with --help or -h for options.
Using a browser, go to http://localhost:3000 and you'll see: "Yay! You’re on Rails!"
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!

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

License