Basic tenets of Ruby on Rails

[archy22]

Convention over Configuration
Rails has sensible defaults for every aspect of a web application. Following the conventions, you can write a Rails application, using less code than most other web application frameworks. If you need to override the conventions, it's also easy with Rails.

Don't Repeat Yourself (DRY)
Every piece of knowledge in a system should be expressed in just one place. From a coding perspective, the means you should not find yourself writing the same lines of functionality in multiple locations within the same application, including in more than one view template. Logic that is repeated should be consolidated into one location.


Fat Model, Skinny Controller
Most of your application logic should be contained in your models, rather than your controllers. Similarly, views should have a minimum of ruby code and more involved logic, such as complex formatting, should be extracted to helpers.

REST interface
REST is a commonly-utilized pattern for web applications - organizing your application around resources and standard HTTP verbs is the fastest way to go. Ruby on Rails provides extensive support for REST patterns by default, making it often the easiest design pattern to employ when using the Rails framework. If you are developing an application and finding that you have to manually create many of the routes and methods for a particular class, it may be worth examining if there is a more RESTful way to implement it. Using scaffolds and Rails metaprogramming (e.g. routing) will also generally encourage REST pattern use.

Write Good Tests
Rails comes with an integrated testing framework out of the box that supports common testing methods including unit and integration testing as well as fixtures. Having reliable tests will help a programmer tremendously when integrating new features or refactoring code – if you have appropriate testing coverage, you can immediately detect if a new change has broken any existing functionality.

Automate tasks
Your Rails project comes with many scripts and generators, which allow you to solve many common tasks in one line in the console. You can start the server, migrate the database, run tests, measure performance and much more with the help of Rake tasks and scripts

[benmoriz]

Automate tasks
Your Rails project comes with many scripts and generators, which allow you to solve many common tasks in one line in the console. You can start the server, migrate the database, run tests, measure performance and much more with the help of Rake tasks and scripts

[njtboy]

REST is a commonly-utilized pattern for web applications - organizing your application around resources and standard HTTP verbs is the fastest way to go. Ruby on Rails provides extensive support for REST patterns by default, making it often the easiest design pattern to employ when using the Rails framework. If you are developing an application and finding that you have to manually create many of the routes and methods for a particular class, it may be worth examining if there is a more RESTful way to implement it. Using scaffolds and Rails metaprogramming (e.g. routing) will also generally encourage REST pattern use.

[bimal chand]

Ruby on Rails, often shortened to Rails, is an open source full-stack web application framework for the Ruby programming language. Ruby on Rails is not to be confused with Ruby, which is a general-purpose programming language, on which Ruby on Rails runs. Ruby itself existed for more than 10 years before the first release of Ruby on Rails. Rails is a full-stack framework, meaning that it gives the web developer the ability to gather information from the web server, talk to or query the database, and render templates out of the box. As a result, Rails features a routing system that is independent of the web server.

[bjkc]

REST is a commonly-utilized pattern for web applications - organizing your application around resources and standard HTTP verbs is the fastest way to go. Ruby on Rails provides extensive support for REST patterns by default, making it often the easiest design pattern to employ when using the Rails framework. If you are developing an application and finding that you have to manually create many of the routes and methods for a particular class, it may be worth examining if there is a more RESTful way to implement it. Using scaffolds and Rails metaprogramming (e.g. routing) will also generally encourage REST pattern use.