<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Ruby on Rails Notes &#187; links</title> <atom:link href="http://railsnotes.com/tag/links/feed/" rel="self" type="application/rss+xml" /><link>http://railsnotes.com</link> <description>A code-heavy brain dump of stuff I come across working on Ruby on Rails projects including Models, ActiveRecord, Views, Controllers, RESTful rails, deployment, server stuff, etc.</description> <lastBuildDate>Sun, 29 Aug 2010 23:45:16 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>Git Workflow</title><link>http://railsnotes.com/442-git-workflow/</link> <comments>http://railsnotes.com/442-git-workflow/#comments</comments> <pubDate>Tue, 05 May 2009 10:20:10 +0000</pubDate> <dc:creator>Melvin Ram</dc:creator> <category><![CDATA[Other]]></category> <category><![CDATA[Git]]></category> <category><![CDATA[links]]></category><guid
isPermaLink="false">http://www.railsnotes.com/?p=442</guid> <description><![CDATA[ReinH &#124; A Git Workflow for Agile Teams Sharing of good work-flow is one of the keys to adoption and effective use of new technology. Git is a relatively new technology and it&#8217;s workflow is not a topic that is discussed often in the Rails community SO it intrigued me when Bryan Liles mentioned the [...]]]></description> <content:encoded><![CDATA[<p></p><p><img
class="alignright size-medium wp-image-452" style="padding: 10px" src="http://www.railsnotes.com/wp-content/uploads/2009/05/creative-flow-directly-from-god1-300x213.jpg" alt="creative-flow-directly-from-god1" width="300" height="213" /></p><p><a
href="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html?dsq=9007869#comment-9007869">ReinH | A Git Workflow for Agile Teams</a></p><p><a
href="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html?dsq=9007869#comment-9007869"></a>Sharing of good work-flow is one of the keys to adoption and effective use of new technology.</p><p>Git is a relatively new technology and it&#8217;s workflow is not a topic that is discussed often in the Rails community SO it intrigued me when <a
href="http://smartic.us/" target="_blank">Bryan Liles</a> mentioned the above article by ReinH in <a
href="http://vimeo.com/4202549">one of his videos</a>. I highly recommend giving it a read as it presents some interesting ideas.</p><p>Here&#8217;s an example. Recently I had a need to build an ecommerce site. <a
href="http://www.Spreehq.org" target="_blank">Spree</a> is a nice open source ecommerce system built on Rails&#8230; however, it does not suit my needs perfectly and when I started looking around the code, I found some code that could be refactored to act more effectively.</p><p>I like to commit often&#8230; sometimes a little too often. Sometimes I&#8217;ll make a change, commit it, do a browser check to see if it works, go back, fix any errors, commit again, and repeat the cycle. The result of my frequent committing is that I have a ton of tiny commits that others won&#8217;t really find useful following along. If they tried, they&#8217;d understand, but they&#8217;d waste a ton of time because the commits are small and often filled with errors that are fixed on the next 2 or 3 commits.</p><p>What should I do? The article by ReinH proposes an answer to the problem. Go check it out! Be sure to not be a passive blog reader. Please leave feedback on what you thought. It acts as fuel for bloggers.</p> ]]></content:encoded> <wfw:commentRss>http://railsnotes.com/442-git-workflow/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Freeze Rails</title><link>http://railsnotes.com/440-freeze-rails/</link> <comments>http://railsnotes.com/440-freeze-rails/#comments</comments> <pubDate>Tue, 05 May 2009 07:11:03 +0000</pubDate> <dc:creator>Melvin Ram</dc:creator> <category><![CDATA[Other]]></category> <category><![CDATA[deployment]]></category> <category><![CDATA[freeze]]></category> <category><![CDATA[links]]></category> <category><![CDATA[rails]]></category> <category><![CDATA[rake]]></category><guid
isPermaLink="false">http://www.railsnotes.com/?p=440</guid> <description><![CDATA[When developing a rails app, it&#8217;s a good idea to &#8220;freeze&#8221; your app. What this means is that you&#8217;re making a copy of rails in your RAILS_APP_ROOT/vendors/rails directory. This will help reduce your dependencies&#8230; just in case you deploy your app to a machine that does not have the version of Rails you used to [...]]]></description> <content:encoded><![CDATA[<p></p><p>When developing a rails app, it&#8217;s a good idea to &#8220;freeze&#8221; your app. What this means is that you&#8217;re making a copy of rails in your RAILS_APP_ROOT/vendors/rails directory. This will help reduce your dependencies&#8230; just in case you deploy your app to a machine that does not have the version of Rails you used to develop it (older or newer.)</p><p>This article covers the topic really well: <a
href="http://www.softiesonrails.com/2008/1/3/freezing-your-rails-application">Softies on Rails: Freezing Your Rails Application</a>.</p><p>One thing it doesn&#8217;t cover is how to freeze a specific version of rails. It&#8217;s pretty simple:</p><pre>rake rails:freeze:gems VERSION=2.1.0</pre><p>This will allow you to run your app against the version of rails your app was written for.</p> ]]></content:encoded> <wfw:commentRss>http://railsnotes.com/440-freeze-rails/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 4/16 queries in 0.038 seconds using disk

Served from: railsnotes.com @ 2010-09-09 07:11:04 -->