Tag Archives: ruby

Your own gem server and Ruby 1.8.5

A while back, I wrote about creating your own gem server - which basically consisted of custom building a sources gem. Mainly because gem sources –remove at the time wouldn’t let you remove rubyforge from the sources list.
Thankfully, gem sources –remove now works great. And with RubyGems 0.9.5 - they’ve included a [...]

Creating Your Own Gem Server

I’ve been hand updating gems for too long on my servers, but I have been hesitant to do anything more automated as long as my systems were updating against http://gems.rubyforge.org. Rubyforge has been down more than once when I really needed to update something, and I don’t want to create an automated dependency on [...]

Don’t Do That

So… maybe you are coding up your totally way rad awesome application in Rails - and you are thinking to yourself.
“Self, I really would like to set my own created_at and updated_at timestamps. Look - there’s even a way to do that in the Rails documentation”

class Feed < ActiveRecord::Base
[...]

p.s. it’s never really about a single post

so I went into snarky overdrive with my vendor dependencies post. it wasn’t quite as funny as last year when I went off on the people that can’t unsubscribe from lists either. Nor was it as funny as some other commentary on Rails I’ve snarkily made
I really do love the err.the.blog guys - [...]

Good Grief People, stop with the local gems

From Err The Blog: Vendor Everything
For hosted environments? sure.
But if you are responsible for the application AND the server? (or your shop is?)
No.
Not just no. But HELL No. And I’d really like to write “HELL No” in an <h1> but I’m going to avoid that for the sake of [...]

No quarters, no nikes, none of the time

Episode moved to its new home at conversationswithplasticdinosaurs.com

Rails 1.2 Route Changes Are a Pain in the Arse

So, the rails routing changes that have apparently happened in Rails 1.2? Yeah - not a fan.
Thankfully, last night, the night before we plan a production transition to Rails 1.2, we got spidered by crawlers looking for old, vulnerable copies of phpMyAdmin - they hit a systems testing server.
I don’t think I’ve [...]

Upgrading your Rails 1.1 application to Rails 1.2

So, I’m in the process of getting our servers upgraded to Rails 1.2.
( We don’t freeze rails, because contrary to the cult of Rails, freezing is not the way to go in small, controlled shops with multiple applications. If say, you have to upgrade your Rails, NOW NOW NOW - it’s much [...]

Dear RubyGems

The fact that you create ~/.gem and stick a source_cache file in there pisses me off royally.
This made me curse you bitterly today. And made Daniel and James laugh at me for doing so.
Of course that made me laugh, but that’s beside the point. I still dislike you royally.
Just want you [...]

require_gem deprecation warnings, redux

So I’ve written about this before - and it turns out that a lot of the “require_gem” deprecation warnings come from tasks in your gem builds that build convenience scripts in /usr/bin (or wherever on your system it places these). So if these convenience scripts (like /usr/bin/mongrel_rails) are left around from installs with previous [...]

Anatomy of a screw up

So, because you’ll learn far more from screwing up, then getting it always right - here’s the latest screw up from yours truly. Documented for all the world to see
So, I have been making slow progress the last few weeks in updating our account registration application to be a bit more normalized, [...]

My, my those deprecation warnings are annoying

Sometimes the interpreted language equivalent of “compiler warnings” get really quite annoying (this might explain why subconsciously I have always been incredibly pedantic about compiler warnings).
Anyway, with advent of RubyGems 0.9.0, the “require gem” command is deprecated.
And as of 0.9.1 of RubyGems (to which you might want to update because of a security hole) - [...]

Man, I like good framworks

In the end it’s all code - but this is the first time I’ve done this and I just think this is the coolest thing that I don’t have to futz with this.
(and by the way, being able to test this in a console - great stuff)

$ script/console
Loading development environment.
>> newposition = Position.new
=> #<Position:0×25489f8 @attributes={”name”=>”", [...]

A better rubygems lister

I’m in the process of teaching myself ruby - first by dealing with the language core and stdlib by just writing ruby (no frameworks) to replace my myriad of crappy shell scripts that I’m using for various things. I can do a lot more quickly in a ruby (or perl or even php) [...]

Fun with FileMerge

So you think you want to be a elite security researcher? Maybe, just maybe, hypothetically - one of your favorite open source projects releases an announcement touting a mysterious, but CRITICAL, GIGANTIC, MOTORCYCLE DEATH MACHINE security hole - so what do you do?
One, you could crash the python-based bug tracking system trying to read [...]

Holy Crap Batman

Wow, abstract routing isn’t all that cool. Particularly if you can game the routes.
And Rails 1.1.5 has its own problems too. As my co-worker said, expect 1.1.6 soon
Notepads and Carrier Pigeons for everyone. Just hope PETA doesn’t complain about the Packet Loss.
p.s. Yes, my theory was [...]

I am not sure this is the best way to learn Ruby

For non-ruby programmers - going through the diff of Ruby 1.1.4 compared to 1.1.5 will make your head swim.
Although I have some theories now on what the 1.1.5 release was/is supposed to fix - but I’m not sure I understand the flow of things enough to be doing anything other than typing out of my [...]

Weyahl There is Gone Be Some Heck to Pay For that

So the happy little Ruby on Rails crew done gone and got themselves a security hole
Their release announcement certainly got my attention. And I’m honestly pretty reactive (”Problem! Problem! Solve it NOW!”) - so after a broadcast to our Rails-developin’ crew - we got on it and got our system and frozen rails [...]