Articles

Ruby on Rails 2.3.4: Security Fixes

Ruby on Rails 2.3.4 released, this release fixes bugs and introduces a few minor features. Due to the inclusion of two security fixes, all users of the 2.3 series are recommended to upgrade as soon as possible.

Security Fixes

2.3.4 contains fixes for two security issues which were reported to us. For more details see the security announcements:

RMagick (from source) on Snow Leopard

After the release of 10.5, I published an article about building RMagick from source on Leopard. I won’t rehash the why, you can read the original article for that. My clean install necessitated updating the RMagick script, so here’s what worked for me to install from source on Snow Leopard! For the impatient, here’s the download link: rmagick-build.sh

Snow Leopard Ruby Development Environment Checklist / Gotchas

I’m probably a bit late to the party with this article, but I’m a bit of a chicken so I thought I’d wait for the dust to settle a bit before installing Snow Leopard on the MacBook Pro I use for Ruby development.

Rails Envy Podcast – Episode #090 – 09/03/2009

Episode #090. I’m joined today by Dan Benjamin and we have quite a fun time. You may know Dan from his compiling Ruby, Rails, and MySQL guides, cork’d, and most recently Playgrounder. Dan’s going to be hosting the podcast for a little while now and I’m thrilled to have him as a co-host.

Installing the Ruby driver for DB2 on Mac OS X Snow Leopard

Now that Mac OS X 10.6 is out, it’s time to leave the world of 32 bit computing behind. The pre-installed Ruby interpreter will run in 64 bit mode by default, so you may need to pay attention when installing some C-based gems. The ibm_db Ruby gem for DB2 can easily be installed or updated to the latest available version by following these simple steps:

That’s Not a Memory Leak, It’s Bloat

Our Rails customers often run into memory issues. The most frequent cause these days is what we in Support dub ‘bloated mongrels.’

To be fair, bloat has absolutely nothing to do with mongrel itself, which is a solid and fine piece of work. You can run into this problem just as easily with thin, passenger, etc. Changing to a different server will not save you, as the root cause is not the server, but the code the server is running for you.

Easy partials

Following code has been tested with Rails 2.3 .

Traditional way of rendering partials.

 
render :partial => 'comments/comment', :locals => { :comment => comment, :show_article_title => false}

Above code can also be written as 

 
render 'comments/comment', :comment => comment, :show_article_title => false

One more example.

Ruby on Rails Security

Recently I've been made aware of people inside US Government organizations using my Ruby on Rails Security presentation as an excuse to limit Ruby on Rails adoption and projects inside those organizations.

They mandate that applications in Rails should be redone in Java because of the issues I covered.

Double Shot #532

Life goes on after Snow Leopard.

set passenger RailsMaxPoolSize / PassengerMaxPoolSize to actually work + how many instances of passenger to have for rails

Passenger seems to ignore trying to set PassengerMaxPoolSize in vhosts.

To set the maximum number of instances for passenger for Rails, set it in a file called passenger.conf and then do this:

OpenVMS | Rails Fire

OpenVMS

In-depth JRuby Q&A: What Makes JRuby Tick in 2010?

JRuby is undoubtedly the most mature of the alternative Ruby implementations. Supporting Ruby 1.8.7 and 1.9.1 (mostly!) and JIT compilation, JRuby is already in use in mission critical Ruby apps and runs scarily fast on the JVM. In this interview with JRuby core member, Charles Nutter, we dig deep into what makes JRuby tick.

J is for JVM: Why the ‘J’ in JRuby?

The current JRuby team members are all passionate hackers with intimate knowledge of Ruby, Java, and of course JRuby. That said, none of us were on the team at the project’s original inception. I assume the JRuby pioneers thought JRuby would be a good idea—I know I did, when I first heard about it. For a lot of folks though, it’s somewhat less obvious. Why is writing JRuby on top of the JVM a good idea, they ask. Are we nuts, evil geniuses, or is using the JVM just a solid pragmatic decision?

Syndicate content