Rails Best Practices, Tips and Tricks - The Diigo Meta page

• 27 Sep 11
  

  Flash D

  ruby rails programming pre-diigo

• 13 Oct 10
  

  Jure S
• 27 Jan 09
  

  Mike Miller

  rails best practices

  • Rails Best Practices, Tips and Tricks
• 28 Jul 08
  

  Vincent Tsao

  Rails Tips Tricks

• 27 Jul 08
  

  A. D.

  ruby rails tips

• 17 May 08
  

  E Young

  single

  rails

• 13 Apr 08
  

  Thomas R. Stegelmann

  tipps rails

• 23 Mar 08
  

  gabriele Domenichini

  programming rails rubyonrails tutorial webdev

• 21 Mar 08
  

  Jeremy Maziarz

  rails

• 08 Mar 08
  

  derekgottlieb

  rails rubyonrails bestpractices tips programming development

• 23 Feb 08
  

  frankalcantara

  rubyonrails tutorials

• 08 Jan 08
  

  Jason Fowler

  raction of SaltedHashLoginGenerator, and as such, has the disadvantages that SaltedHash has. Additionally, it uses the Rails Engines system which is designed for drop in use. In general, applications need customization. If you need more than simple modifi

  rails rubyonrails bestpractices tips programming development howto ruby cheatsheet

• 19 Dec 07
  

  ratbeard

  rails tdd tips

• 05 Oct 07
  

  ruby-and-rails

• 09 Sep 07
  

  Harjeet Singh

  best practices bookmark rails

• 23 Aug 07
  

  Lenin Torres

  rails

• 20 Aug 07
  

  Hendy Irawan

  This is absolutely essential. Rails makes writing unit and functional tests incredibly easy and testing should be employed at all times. Positive and negative testing should be employed: the first to verify that the application does what it is supposed to

  active ajax authentication blog blogs books database design

• 31 Jul 07
  

  adam smith

  rubyonrails

• 07 Jun 07
  

  lgsiigo

  rails tutorial programming top::rails::tutorial

• 17 May 07
  

  gilles_tasse

  Book too bye

• 02 Apr 07
  

  josefbauer888

  Technologie Ruby on Rails

• 27 Mar 07
  

  Danny

  bestpractices delicious ruby rubyonrails tips

• 21 Mar 07
  

  Michael Hamann

  rails ruby RubyonRails programming tips bestpractices development webdesign guide patterns snippets softwaredevelopment blog design

• 08 Feb 07
  

  Jérémy Chatard

  rails best practice tips tricks records active blog development Reference rubyonrails Ruby

• 12 Jan 07
  

  Helmut Sins

  rails ruby rubyonrails programming tips bestpractices

• 19 Dec 06
  

  Frank Colcord

  Ruby

• 15 Dec 06
  

  Johan Van Mol

  imported Bookmarks Ruby_On_Rails rails ruby rubyonrails programming tips bestpractices development johan_vm

• 14 Nov 06
  

  harry

  • Authentication Systems

      

    Several authentication modules have been written for Rails, but some are better at some things and some are better than others.
  • Some sort of source control should be used at all times. This allows for easy roll back if something goes wrong as well as the ability to refer back to old code if needed. Rails has certain files which should not be included in a source control repository, so please refer to the wiki page when preparing the initial import.
  • Don’t use abbreviations, especially in database column names. It should be immediately obvious what the column is for (or atleast what the name means) when looking at the name. These are not the days of C, we don’t need to conserve space with our variable names. Additionally, Rails error handling automatically knows how to “humanize” column names, so when you use a well described name you get to work less on outputting errors.
  • you may want to look into extracting that code to a helper function or partial.
  • You should always run svn update before generating a migration so you don’t have prefix collisions
  • Migrations mean never having to say you’re sorry because you nuked the database. They allow for database agnostic schemas which means you can develop locally on SQLite and deploy on MySQL without a problem. They’re cleaner (and easier) than writing your own schemas custom and should be used whenever possible.
  • Functional testing is used to test controllers.
  • As a general rule, unit testing should test any validation in models as well as any added methods in those models
  • NEVER EVER EVER modify schema.rb. It is a reflection of the database. Migrations should be used to move this forward. If you don’t use migrations and instead modify schema.rb, things will break and people will be unhappy.

  7 more annotations...

• 07 Nov 06
  

  Vishnu Gopal

  imported Interesting rails ruby rubyonrails programming tips delicious_import

• 31 Oct 06
  

  Łukasz Piestrzeniewicz

  ruby rubyonrails best practices

• 24 Oct 06
  

  Marcin Bajer

  Ruby reference development from-delicious

• 30 Aug 06
  

  Tad Donaghe

  rails ruby rubyonrails bestpractices toread

• 07 Aug 06
  

  まくりねっと

  ruby

• 06 Aug 06
  

  hanakuso

  ruby

• 02 Aug 06
  

  Jamie Dinkelacker

  programming rubyonrails softdev

• 20 Jul 06
  

  Dong Zhang

  rails

• 25 Jun 06
  

  greenbes

  ruby

• 12 Jun 06
  

  jschoolcraft

  Rails best practices

  ruby rails BestPractices

• 29 May 06
  

  Marcio Barrios

  rails tips

• 10 May 06
  

  Jivko Georgiev

  rails blogs

• 12 Apr 06
  

  miles woodroffe

  programming rubyonrails bestpractices

• 11 Apr 06
  

  Esteban Trigos

  rubyonrails

• 25 Mar 06
  

  rails

• 24 Mar 06
  

  Frank Baxter

  ruby rails

• 23 Mar 06
  

  Anton Hipertracker

  rubyonrails

• 15 Mar 06
  

  Bruce Healy

  rails rubyonrails best practices

• 09 Mar 06
  

  dbhumphreys

  home of misc. useful rails articles

  comp_ruby

• 08 Mar 06
  

  Maggie Tsai

  rails ruby

  • Testing

      

    This is absolutely essential. Rails makes writing unit and functional tests incredibly easy and testing should be employed at all times. Positive and negative testing should be employed: the first to verify that the application does what it is supposed to when the proper variables are passed to the correct action and then second to verify that when incorrect variables are passed the prefered behavior occurs.

  • Migrations

      

    Migrations mean never having to say you’re sorry because you nuked the database. They allow for database agnostic schemas which means you can develop locally on SQLite and deploy on MySQL without a problem. They’re cleaner (and easier) than writing your own schemas custom and should be used whenever possible.
• 07 Mar 06
  

  Bill Christian

  ruby

• 02 Mar 06
  

  Antonio Yon

  rubyonrails development

• 17 Feb 06
  

  phersh

  Good points to keep in mind when working with rails.

  rails best practices authentication login

• 10 Feb 06
  

  Benoit Caron

  ruby rubyonrails tips webapp oldies

• 09 Feb 06
  

  Alan Ho

  programming rails ruby pattern

• 08 Feb 06
  

  Darko Bodnaruk

  rails

• 

  David Fontanella

  rails programming Ruby

• 

  Marcello Morsello

  rails

• 07 Feb 06
  

  jiggsfoo

  rails programming ruby

• 

  Rails Ruby

• 

  G B

  ruby rails programming

• 

  Adnan Balagamwala

  rails

• 

  Michael Caldwell

  programming rails ruby best_practice

• 

  erik pettersen

  ruby rubyonrails ajax

• 

  Miska Lahti

  "Because Rails is a young framework, I thought it would be helpful to write up what I consider best practices when coding with it both for my new coworkers and the web at large. Here’s my current draft."

  programming ruby rails

• 

  vladimir liba

  programming rails tips

• 

  Jason Reis

  rails tips

• 

  Ignacio Silva

  rails

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.