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
Anton Khamets 7c89948c41 Extend image_tag to accept ActiveStorage Attachments and Variants (#30084)
* Extend image_tag to accept ActiveStorage's Attachments and Variants

* Flip resolve_image_source around

* Add tests for the new use-cases of image_tag

* Remove the higher-level test

* Update image_tag documentation

* Add error states into the test suite

* Re-raise polymorhic_url's NoMethodError as ArgumentError

* delegate_missing_to will raise DelegationError instead of NoMethodError
2017-08-07 09:38:51 -05:00
.github Limit stale checks to issues 2017-04-01 11:27:26 -05:00
actioncable Lint actioncable/CHANGELOG.md 2017-08-06 22:14:10 -04:00
actionmailer Remove outdated comment [ci skip] 2017-08-06 04:20:16 +02:00
actionpack Lint actionpack/CHANGELOG.md 2017-08-06 22:17:35 -04:00
actionview Extend image_tag to accept ActiveStorage Attachments and Variants (#30084) 2017-08-07 09:38:51 -05:00
activejob Use File::NULL instead of "/dev/null" 2017-07-31 21:58:42 +09:00
activemodel Talk about bytes not characters 2017-07-31 17:42:43 -04:00
activerecord Lint activerecord/CHANGELOG.md 2017-08-06 22:24:30 -04:00
activestorage Extend image_tag to accept ActiveStorage Attachments and Variants (#30084) 2017-08-07 09:38:51 -05:00
activesupport Extend image_tag to accept ActiveStorage Attachments and Variants (#30084) 2017-08-07 09:38:51 -05:00
ci Use File::NULL instead of "/dev/null" 2017-07-31 21:58:42 +09:00
guides Capitalize Rake 2017-08-06 22:54:23 -04:00
railties Lint railties/CHANGELOG.md 2017-08-06 22:32:26 -04:00
tasks Merge pull request #30020 from rails/active-storage-import 2017-08-04 18:05:13 -05:00
tools * Don't eagerly require Rails' minitest plugin. 2017-07-10 20:40:16 +02:00
.codeclimate.yml
.gitattributes
.gitignore Test rails-ujs in our travis matrix 2017-02-22 13:49:28 -05:00
.rubocop.yml Do not change the entire codebase style only because of active_storage 2017-08-03 17:45:58 -04:00
.travis.yml Setup travis to be able to run CI tests against S3 2017-07-31 17:51:16 -05:00
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md Remove html tag making markdown misrender [ci skip] 2017-06-05 22:11:57 -05:00
Gemfile Depend on offical azure-core 2017-08-03 12:12:58 +02:00
Gemfile.lock Depend on offical azure-core 2017-08-03 12:12:58 +02:00
MIT-LICENSE Bump license years for 2017 2016-12-31 08:34:08 -05:00
rails.gemspec Bring activestorage dependencies into the general Gemfile 2017-07-31 15:53:09 -05:00
RAILS_VERSION Start Rails 5.2 development 2017-03-22 10:11:39 +10:30
Rakefile Add task to verify a release. 2017-07-22 21:17:25 +02:00
README.md Add Active Storage to README and release (#30065) 2017-08-04 17:55:24 -05:00
RELEASING_RAILS.md Update release instructions in light of new tasks. 2017-07-22 21:17:44 +02:00
version.rb Revert "Merge pull request #29540 from kirs/rubocop-frozen-string" 2017-07-02 02:15:17 +09:30

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; Active Storage (README), a library to attach cloud and local files to Rails applications; 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

  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
     $ rails server
    

    Run with --help or -h for options.

  4. Using a browser, 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.