Ruby on Rails

Ruby on Rails
Original author(s) David Heinemeier Hansson
Initial release 13 December 2005 (2005-12-13)[1]
Stable release 5.1.3 (August 3, 2017 (2017-08-03)[2]) [±]
Repository github.com/rails/rails
Development status Active
Written in Ruby
Operating system Cross-platform
Size 18.2 MB[3]
Type Web application framework
License MIT License
Website rubyonrails.org

Ruby on Rails, or simply Rails, is a server-side web application framework written in Ruby under the MIT License. Rails is a model–view–controller (MVC) framework, providing default structures for a database, a web service, and web pages. It encourages and facilitates the use of web standards such as JSON or XML for data transfer, and HTML, CSS and JavaScript for display and user interfacing. In addition to MVC, Rails emphasizes the use of other well-known software engineering patterns and paradigms, including convention over configuration (CoC), don't repeat yourself (DRY), and the active record pattern.[4]

History

David Heinemeier Hansson extracted Ruby on Rails from his work on the project management tool Basecamp at the web application company also called Basecamp.[5] Hansson first released Rails as open source in July 2004, but did not share commit rights to the project until February 2005. In August 2006, the framework reached a milestone when Apple announced that it would ship Ruby on Rails with Mac OS X v10.5 "Leopard",[6] which was released in October 2007.

Rails version 2.3 was released on March 15, 2009 with major new developments in templates, engines, Rack and nested model forms. Templates enable the developer to generate a skeleton application with custom gems and configurations. Engines give developers the ability to reuse application pieces complete with routes, view paths and models. The Rack web server interface and Metal allow one to write optimized pieces of code that route around Action Controller.[7]

On December 23, 2008, Merb, another web application framework, was launched, and Ruby on Rails announced it would work with the Merb project to bring "the best ideas of Merb" into Rails 3, ending the "unnecessary duplication" across both communities.[8] Merb was merged with Rails as part of the Rails 3.0 release.[9][10]

Rails 3.1 was released on August 31, 2011, featuring Reversible Database Migrations, Asset Pipeline, Streaming, jQuery as default JavaScript library and newly introduced CoffeeScript and Sass into the stack.[11]

Rails 3.2 was released on January 20, 2012 with a faster development mode and routing engine (also known as Journey engine), Automatic Query Explain and Tagged Logging.[12] Rails 3.2.x is the last version that supports Ruby 1.8.7.[13] Rails 3.2.12 supports Ruby 2.0.[14]

Rails 4.0 was released on June 25, 2013, introducing Russian Doll Caching, Turbolinks, Live Streaming as well as making Active Resource, Active Record Observer and other components optional by splitting them as gems.[15]

Rails 4.1 was released on April 8, 2014, introducing Spring, Variants, Enums, Mailer previews, and secrets.yml.[16]

Rails 4.2 was released on December 19, 2014, introducing Active Job, asynchronous emails, Adequate Record, Web Console, and foreign keys.[17]

Rails 5.0 was released on June 30, 2016, introducing Action Cable, API mode, and Turbolinks 5.[18]

Rails 5.0.0.1 was released on August 10, 2016 with Exclusive use of rails CLI over Rake and supports Ruby 2.2.2+ versions

Rails 5.1 was released on April 27, 2017, introducing Javascript integration changes (management of JavaScript dependencies from NPM via Yarn, optional compilation of JavaScript using Webpack, and a rewrite of Rails UJS to use vanilla JavaScript instead of depending on jQuery), system tests using Capybara, encrypted secrets, parameterized mailers, direct & resolved routes, and a unified form_with helper replacing the form_tag/form_for helpers.[19]

Version history
Version Date
1.0[20] December 13, 2005
1.2[21] January 19, 2007
2.0[22] December 7, 2007
2.1[23] June 1, 2008
2.2[24] November 21, 2008
2.3[25] March 16, 2009
3.0[26] August 29, 2010
3.1[27] August 31, 2011
3.2[28] January 20, 2012
4.0[29] June 25, 2013
4.1[16] April 8, 2014
4.2[17] December 19, 2014
4.2.5 November 13, 2015
5.0[18] June 30, 2016
5.0.1[30] December 21, 2016
5.1[19] May 10, 2017

Technical overview

Like many web frameworks, Ruby on Rails uses the model–view–controller (MVC) pattern to organize application programming.

In a default configuration, a model in the Ruby on Rails framework maps to a table in a database and to a Ruby file. For example, a model class User will usually be defined in the file 'user.rb' in the app/models directory, and linked to the table 'users' in the database. While developers are free to ignore this convention and choose differing names for their models, files, and database table, this is not common practice and is usually discouraged in accordance with the "convention-over-configuration" philosophy.

A controller is a server-side component of Rails that responds to external requests from the web server to the application, by determining which view file to render. The controller may also have to query one or more models for information and pass these on to the view. For example, in an airline reservation system, a controller implementing a flight-search function would need to query a model representing individual flights to find flights matching the search, and might also need to query models representing airports and airlines to find related secondary data. The controller might then pass some subset of the flight data to the corresponding view, which would contain a mixture of static HTML and logic that use the flight data to create an HTML document containing a table with one row per flight. A controller may provide one or more actions. In Ruby on Rails, an action is typically a basic unit that describes how to respond to a specific external web-browser request. Also, note that the controller/action will be accessible for external web requests only if a corresponding route is mapped to it. Rails encourages developers to use RESTful routes, which include actions such as create, new, edit, update, destroy, show, and index. These mappings of incoming requests/routes to controller actions can be easily set up in the routes.rb configuration file.

A view in the default configuration of Rails is an erb file, which is evaluated and converted to HTML at run-time. Alternatively, many other templating systems can be used for views.

Ruby on Rails includes tools that make common development tasks easier "out-of-the-box", such as scaffolding that can automatically construct some of the models and views needed for a basic website.[31] Also included are WEBrick, a simple Ruby web server that is distributed with Ruby, and Rake, a build system, distributed as a gem. Together with Ruby on Rails, these tools provide a basic development environment.

Ruby on Rails is most commonly not connected to the Internet directly, but through some front-end web server. Mongrel was generally preferred over WEBrick in the early days, but it can also run on Lighttpd, Apache, Cherokee, Hiawatha, Nginx (either as a module – Phusion Passenger for example – or via CGI, FastCGI or mod_ruby), and many others. From 2008 onwards, Passenger replaced Mongrel as the most-used web server for Ruby on Rails.[32] Ruby is also supported natively on the IBM i.[33]

Ruby on Rails is also noteworthy for its extensive use of the JavaScript libraries, Prototype and Script.aculo.us, for scripting Ajax actions.[34] Ruby on Rails initially utilized lightweight SOAP for web services; this was later replaced by RESTful web services. Ruby on Rails 3.0 uses a technique called Unobtrusive JavaScript to separate the functionality (or logic) from the structure of the web page. jQuery is fully supported as a replacement for Prototype and is the default JavaScript library in Rails 3.1, reflecting an industry-wide move towards jQuery. Additionally, CoffeeScript was introduced in Rails 3.1 as the default Javascript language.

Since version 2.0, Ruby on Rails offers both HTML and XML as standard output formats. The latter is the facility for RESTful web services.

Rails 3.1 introduced Sass as standard CSS templating.

By default, the server uses Embedded Ruby in the HTML views, with files having an html.erb extension. Rails supports swapping-in alternative templating languages, such as HAML and Mustache.

Ruby on Rails 3.0 has been designed to work with Ruby 1.8.7, Ruby 1.9.2, and JRuby 1.5.2+; earlier versions are not supported.[35]

Ruby on Rails 3.2 is the last series of releases that support Ruby 1.8.7.

Framework structure

Ruby on Rails is separated into various packages, namely ActiveRecord (an object-relational mapping system for database access), Active Resource (provides web services), Action Pack, Active Support and Action Mailer. Prior to version 2.0, Ruby on Rails also included the Action Web Service package that is now replaced by Active Resource. Apart from standard packages, developers can make plugins to extend existing packages. Earlier Rails supported plugins within their own custom framework; version 3.2 deprecates these in favor of standard Ruby "gems".[36]

Deployment

Ruby on Rails is often installed using RubyGems, a package manager[37] which is included with current versions of Ruby. Many free Unix-like systems also support installation of Ruby on Rails and its dependencies through their native package management system.

Ruby on Rails is typically deployed with a database server such as MySQL or PostgreSQL, and a web server such as Apache running the Phusion Passenger module.

Philosophy and design

Ruby on Rails is intended to emphasize Convention over Configuration (CoC), and the Don't Repeat Yourself (DRY) principle.

"Convention over Configuration" means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called sales by default. It is only if one deviates from this convention, such as calling the table "products sold", that the developer needs to write code regarding these names. Generally, Ruby on Rails conventions lead to less code and less repetition.[38]

"Don't repeat yourself" means that information is located in a single, unambiguous place. For example, using the ActiveRecord module of Rails, the developer does not need to specify database column names in class definitions. Instead, Ruby on Rails can retrieve this information from the database based on the class name.

"Fat models, skinny controllers" means that most of the application logic should be placed within the model while leaving the controller as light as possible.

Trademarks

In March 2007, David Heinemeier Hansson filed three Ruby on Rails-related trademark applications to the USPTO. These applications regard the phrase "RUBY ON RAILS",[39] the word "RAILS",[40] and the official Rails logo.[41] As a consequence, in the summer of 2007, Hansson denied permission to Apress to use the Ruby on Rails logo on the cover of a new Ruby on Rails book written by some authoritative community members. The episode gave rise to a polite protest in the Ruby on Rails community.[42][43] In response to this criticism, Hansson replied:

I only grant promotional use [of the Rails logo] for products I'm directly involved with. Such as books that I've been part of the development process for or conferences where I have a say in the execution. I would most definitely seek to enforce all the trademarks of Rails.[42]

Reception

Scalability

Rails running on Matz's Ruby Interpreter (the de facto reference interpreter for Ruby) had been criticized for issues with scalability.[44] These critics often mentioned various Twitter outages in 2007 and 2008, which spurred Twitter's partial transition to Scala (which runs on the Java Virtual Machine) for their queueing system and other middleware.[45][46] The user interface aspects of the site continued to run Ruby on Rails[47] until 2011 when it was replaced due to concerns over performance[48]

In 2011, Gartner Research noted that despite criticisms and comparisons to Java, many high-profile consumer web firms are using Ruby on Rails to build scalable web applications. Some of the largest sites running Ruby on Rails include Airbnb, GitHub, Scribd, Shopify, Hulu, and Basecamp.[49] As of January 2016, it is estimated that more than 1.2 million web sites are running Ruby on Rails.[50][51]

Security

In March 2012, security researcher Egor Homakov discovered a "mass assignment" vulnerability that allowed certain Rails applications to be remotely exploited, and demonstrated it by non-maliciously hacking GitHub after his earlier attempts at responsible disclosure were dismissed.[52]

On September 24, 2013, a session cookie persistence security flaw was reported in Ruby on Rails. In a default configuration, the entire session hash is stored within a session cookie known as CookieStore, allowing any authenticated session possessing the session cookie to log in as the target user at any time in the future. As a workaround, administrators are advised to configure cookies to be stored on the server using mechanisms such as ActiveRecordStore.[53]

Researchers Daniel Jackson and Joseph Near developed a data debugger they called "Space" that can analyze the data access of a Rails program and determine if the program properly adheres to rules regarding access restrictions. On April 15, 2016, Near reported that an analysis of 50 popular Web applications using Space uncovered 23 previously unknown security flaws.[54]

References

  1. ↑ David. "Rails 1.0: Party like it's one oh oh!". Ruby on Rails. Retrieved 2017-03-01.
  2. ↑ kaspth. "Rails 5.1.3 released". Ruby on Rails. Retrieved 2017-08-04.
  3. ↑ "Release v5.1.1 · rails/rails · GitHub". Retrieved 25 June 2017.
  4. ↑ "Getting Started with Rails: What Is Rails?". Ruby on Rails Guides. Retrieved 10 August 2014.
  5. ↑ Grimmer, Lenz−− (February 2006). "Interview with David Heinemeier Hansson from Ruby on Rails". MySQL AB. Archived from the original on February 25, 2013. Retrieved 2008-06-08.
  6. ↑ Hansson, David (August 7, 2006). "Ruby on Rails will ship with OS X 10.5 (Leopard)". Retrieved 2008-06-08.
  7. ↑ Hansson, David (March 16, 2009). "Rails 2.3: Templates, Engines, Rack, Metal, much more!".
  8. ↑ "The day Merb joined Rails". 2008-12-27.
  9. ↑ "Ruby on Rails 3.0 Release Notes — Ruby on Rails Guides". Edgeguides.rubyonrails.org. Retrieved 2017-05-24.
  10. ↑ "Ruby on Rails 3.0 goes modular". sdtimes.com. 2010-02-10. Retrieved 2010-08-06.
  11. ↑ "Ruby on Rails 3.1 Release Notes". 2012-09-01.
  12. ↑ "Ruby on Rails 3.2 Release Notes". 2012-09-01.
  13. ↑ "Rails/master is now 4.0.0.beta". 2012-09-01.
  14. ↑ Rails 3.2.x is now compatible with Ruby 2.0.0 by sikachu · Pull Request #9406 · rails/rails · GitHub. Github.com. Retrieved on 2014-05-30.
  15. ↑ "Rails 4.0: Final version released! | Riding Rails". Weblog.rubyonrails.org. 2013-06-25. Retrieved 2017-05-24.
  16. 1 2 "Rails 4.1.0: Spring, Variants, Enums, Mailer previews, secrets.yml". weblog.rubyonrails.org.
  17. 1 2 "Rails 4.2: Active Job, Asynchronous Mails, Adequate Record, Web Console, Foreign Keys". Ruby on Rails. Retrieved 5 Dec 2015.
  18. 1 2 "Rails 5.0: Action Cable, API mode, and so much more". Ruby on Rails. Retrieved 19 Nov 2016.
  19. 1 2 "Rails 5.1: Loving JavaScript, System Tests, Encrypted Secrets, and more". Ruby on Rails. Retrieved 10 May 2017.
  20. ↑ "Rails 1.0: Party like it's one oh oh!". Riding Rails. Retrieved June 9, 2010.
  21. ↑ "Rails 1.2: REST admiration, HTTP lovefest, and UTF-8 celebrations". Riding Rails. Retrieved June 9, 2010.
  22. ↑ "Rails 2.0: It's done!". Riding Rails. Retrieved June 9, 2010.
  23. ↑ Rails 2.1: Time zones, dirty, caching, gem dependencies, caching, etc. Riding Rails. Retrieved June 9, 2010.
  24. ↑ "Rails 2.2: i18n, HTTP validators, thread safety, JRuby/1.9 compatibility, docs". Riding Rails. Retrieved June 9, 2010.
  25. ↑ "Rails 2.3: Templates, Engines, Rack, Metal, much more!". Riding Rails. Retrieved June 9, 2010.
  26. ↑ "Rails 3.0: It's ready!". Riding Rails. Retrieved August 30, 2010.
  27. ↑ "bumping to 3.1.0". Github.com.
  28. ↑ "Preparing for 3.2.0 release". Github.com.
  29. ↑ "Rails 4 in 30’". blog.wyeworks.com.
  30. ↑ "Rails 5.0.1 has been released!". Ruby on Rails. Retrieved 21 Dec 2016.
  31. ↑ Sean Lynch (2007-12-15). "fairleads: Rails 2.0 and Scaffolding Step by Step". Fairleads.blogspot.com. Retrieved 2017-05-24.
  32. ↑
  33. ↑ Maxcer, Chris. "PowerRuby Brings Enterprise Ruby on Rails Support to IBM i". iPro Developer. Retrieved 9 May 2014.
  34. ↑ Js_Escape_Map. "ActionView::Helpers::JavaScriptHelper". Api.rubyonrails.org. Retrieved 2017-05-24.
  35. ↑ "Rails 3.0: It's ready!". rubyonrails.org. Retrieved 2010-08-30. Rails 3.0 has been designed to work with Ruby 1.8.7, Ruby 1.9.2, and JRuby 1.5.2+.
  36. ↑ "Rails 3.2.0.rc2 has been released!". Weblog.rubyonrails.org. 2012-09-01.
  37. ↑ "Ruby on Rails: Download". RubyonRails.org.
  38. ↑ "Getting Started with Rails". Rubyonrails.org. Retrieved 2014-03-10.
  39. ↑ ""Ruby on Rails" Trademark Status". USPTO. Retrieved 2007-08-01.
  40. ↑ ""Rails" Trademark Status". USPTO. Retrieved 2007-08-01.
  41. ↑ "Rails Logo Trademark Status". USPTO. Retrieved 2007-08-01.
  42. 1 2 Forde, Pete (2007-07-23). "Beginning Rails: From Novice to Professional". Archived from the original on August 5, 2007. Retrieved 2007-08-01.
  43. ↑ Cooper, Peter (2007-07-24). "David Heinemeier Hansson says No to Use of Rails Logo". Retrieved 2007-08-01.
  44. ↑ "5 Question Interview with Twitter Developer Alex Payne". radicalbehavior.com. 2007-03-29. Archived from the original on April 23, 2009. Retrieved 2014-11-04. By various metrics Twitter is the biggest Rails site on the net right now. Running on Rails has forced us to deal with scaling issues - issues that any growing site eventually contends with – far sooner than I think we would on another framework.
  45. ↑ Steve Jenson; Alex Payne & Robey Pointer interview (2009-04-03). "Twitter on Scala". artima.com. Retrieved 2009-07-18. We had a Ruby-based queuing system that we used for communicating between the Rails front ends and the daemons, and we ended up replacing that with one written in Scala. The Ruby one actually worked pretty decently in a normal steady state, but the startup time and the crash behavior were undesirable.
  46. ↑ "Twitter jilts Ruby for Scala". theregister.co.uk. 2009-04-01. Retrieved 2009-07-18. By the end of this year, Payne said, Twitter hopes to have its entire middleware infrastructure and its APIs ported to the new language. Ruby will remain, but only on the front end. "We're still happy with Rails for building user facing features... performance-wise, it's fine for people clicking around web pages. It's the heavy lifting, asynchronous processing type of stuff that we've moved away from."
  47. ↑ ryan king (2009-09-25). "Twitter on Ruby". evan weaver. Retrieved 2009-09-29. We use Scala for a few things at Twitter, but the majority of the site is Ruby.
  48. ↑ "Twitter Search is Now 3x Faster". Twitter. Retrieved June 6, 2014.
  49. ↑ "Here's Why Ruby On Rails Is Hot". Business Insider. Retrieved February 10, 2012.
  50. ↑ "Ruby on Rails Usage Statistics". trends.builtwith.com. Retrieved 2016-01-04.
  51. ↑ "Ruby on Rails Token Usage Statistics". trends.builtwith.com. Retrieved 2016-01-04.
  52. ↑ Protalinski, Emil. "How GitHub handled getting hacked". Zdnet.com. Retrieved 2017-05-24.
  53. ↑ Brook, Chris (2013-09-25). "Security Issue in Ruby on Rails Could Expose Cookies". Threat Post. The Kaspersky Lab Security News Service. Retrieved 2014-06-04.
  54. ↑ "Patching up Web applications". MIT News. Retrieved 2016-04-21.

Bibliography

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.