Published Tagged Rails

http://blog.leetsoft.com/2008/11/15/passenger

http://www.rorsecurity.info/the-book/

https://rubyrags.com/

http://ec2onrails.rubyforge.org
http://pauldowman.com/projects/ruby-on-rails-ec2/

http://www.loudthinking.com/posts/21-the-deal-with-shared-hosts

Awesome blog post by DHH. There's a general message here to anyone using open source software: if the software doesn't do what you need it to, YOU should extend it (and even better, submit it back to the community) and not expect the core developers to do the work. They'll do the work IF they want to, probably only if it scratches their own itch or the itches of a lot of people.

Having said that, people should still make suggestions to the core group, but the core group gets to decide their own priorities. Suggestions instead of bitching or demanding or threatening. It's all in the delivery.

Bitching about making money from open source software is even worse. What the hell, Dreamhost? Ditch Rails if it's too much of a pain, we don't need you in our community if you're going to act like that.

http://www.zedshaw.com/rants/rails_is_a_ghetto.html

Not just interesting because it's about Rails, but it's also about open source projects and how the egos interact. The delivery is ... interesting, but it gets the point across.

http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/

http://weblog.rubyonrails.org/2007/12/7/rails-2-0-it-s-done

Ryan Daigle:
http://ryandaigle.com/articles/2007/12/7/rails-2-0-final-released-summary-of-features

http://foss4r.dyndns.org/trac/wiki/ComparingRailsGeoPlugins

"This table gives an initial feature comparison of the various Ruby on Rails plugins available for working with geo data. The idea is to give a quick overview of which plugins are intended for which uses:"

Direct competition for Rails in the Ruby framework space:
http://merbivore.com

From the Merb front page:
"Like Ruby on Rails, Merb is an MVC framework. Unlike Rails, Merb is ORM-agnostic, JavaScript library agnostic, and template language agnostic, preferring plugins that add in support for a particular feature rather than trying to produce a monolithic library with everything in the core. In fact, this is a guiding principle of the project, which has led to third-party support for the ActiveRecord, DataMapper, and Sequel ORMs."

http://marklunds.com/articles/one/374

http://hivelogic.com/narrative/articles/ruby-rails-mongrel-mysql-osx

http://jxh.bingodisk.com/bingo/public/presentations/JHoffmanRailsConf-Berlin-Sept2007.pdf

Jason Hoffman PhD, Founder and CTO, Joyent
Rails Conf Europe 2007
Monday, September 17, 2007

Joyent bought up TextDrive, a well-known Rails host.

http://peepcode.com/products/rails2-pdf

A concise look at some of the new features coming up in Rails 2.0

http://blog.wekeroad.com/2007/10/10/imploding-rails-jesus-dhh-and-the-uncle-ben-principle/

and the follow up blog post:
http://blog.wekeroad.com/2007/10/12/oh-look-darth-vaders-wearing-black-today/

Here's the problem with Rob's thesis: open source doesn't work like that. If you want to extend an open source project in some direction, like improving perf, you do it yourself and contribute back to Rails. The Rails guys are concentrating on moving Rails forward in their own selfish directions, and that's the best way that open source projects grow.

I actually *like* DHH's "I’m not in this world to create Rails for you" attitude. Linux is run the same way. If Rob wants to run his ASP.NET port of Rails in a different way, all the power to him. But as users of an open source project, it's not our place to criticize if we're not contributing major pieces of code back.

http://www.rubyinside.com/19-rails-tricks-most-rails-coders-dont-know-131.html

Done: http://code.google.com/p/audit-mass-assignment/

This was my TODO item:
Make a plugin that warns if no attributes in an ActiveRecord model object are available via attr_accessible because that means no attributes are protected from mass assignment exploits.

Could also make a rake task to run a security audit, with audit checks of your choice provided by additional plugins: rake test:audit

Why are "mass assignment" exploits important for Rails applications? See these links:

1. rorsecurity.info: Do not create records directly from form parameters
http://www.rorsecurity.info/2007/03/20/do-not-create-records-directly-from-form-parameters/

2. Railscasts: Hackers Love Mass Assignment
http://railscasts.com/episodes/26

3. Rails Manual: Typical mistakes in Rails applications: Creating records directly from form parameters
http://manuals.rubyonrails.com/read/chapter/47

http://confreaks.com/

http://www.noobkit.com

http://pragmaticprogrammer.com/titles/fr_deploy/

Authors run Rails host EngineYard:
http://www.engineyard.com/

http://blog.hasmanythrough.com/2007/7/14/validate-your-existence

http://weblog.jamisbuck.org/2007/7/22/capistrano-2-0

http://railscasts.com/

http://blog.caboo.se/articles/2007/7/29/scale-rails-from-one-box-to-three-four-and-five