.

Breezy + Rails == No Go

Ok so it turns out that the current version of Ubuntu (5.10 aka Breezy Badger) ships with Ruby 1.8.3. This is the only version that is NOT COMPATIBALE with Rails. (Debian stable has 1.8.2 so this isn’t a problem there) You have two options - you can try and find a way to get 1.8.2 on your box (Go back to Hoary) or you can go forward (Dapper). If you know me, you already know which direction I went.

The good news about this process is that the install is seriously simple. Truth be told, Ruby would probably be a fine canidate for a backport except for the fact that the package generates a lot of libraries - which they won’t backport.

So let’s get started:

become root

sudo su -

Add the following lines to my /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu dapper main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu dapper main restricted universe multiverse


apt-get update

Now get the dependencies

apt-get build-dep ruby1.8 -tdapper

Now you need to get the source pacakage

apt-get source -b ruby1.8 -tdapper

Wait for it to finish

dpkg -i *.deb

That’s it - and so far it seems to work just fine!


FYI

MySQL 5.0 Reference Manual :: 1.4 Overview of the MySQL Database Management System
The official way to pronounce “MySQL” is “My Ess Que Ell” (not “my sequel”), but we don’t mind if you pronounce it as “my sequel” or in some other localized way.


Live From The Field

Enjoying a Ju Ju Ginger on tap at the flying saucer memphis,tn. Fresh the ginger taste is greater

DirkPhoto071.jpg

Live From The Field

Oh joy - jury duty…

DirkPhoto066.jpg

Live From The Field

A valiant attempt to convince wine drinkers that a cork is bad

DirkPhoto065.jpg

Ways to make brewing better for the environment

Wired News:
But Brooklyn Brewery isn’t alone in its conservation efforts. New Belgium Brewery in Fort Collins, Colorado, has developed a unique method that uses its waste to power its factory.


onegoodmove: Oath Of Office

onegoodmove: Oath Of Office
Raskin: “Senator, when you took your oath of office, you placed your hand on the Bible and swore to uphold the Constitution. You did not place your hand on the Constitution and swear to uphold the Bible.”


:::…Lebowski Fest…:::

OK I admit I was amused by the Goonies 20th anniversary celebration. I had no idea that The Big Lebowski has such a following….

:::…Lebowski Fest…:::

Maybe I need to see it again…


created_at + Postgres == Badness

Ok so it turns out there is a known bug when you use created_at with Postgres. This is apparently going to be fixed in Rails 1.1. The annoying part about it was that it only shows up if you are not restarting your server all the time. Which means in development you probably won’t see it - but in production you will. Very annoying!

That being said it is a perfect oppotunity to talk about plugins. Plugins serve two different purposes:

The first, and probably most common, is to extend Rails in one way or another. This is basically adding new functionality to rails. Examples of this type abound - namely - acts_ad_taggable which makes it trivial to support tagging in your rails apps or Open Laszlo Plugin which builds a bridge from Rails to the Flash capabilities of Open Laszlo.

Basically the plugin allows Rails to do something it has never been able to do before. This is actually handy when you have base level concepts that you want to use across projects. I’m currently playing with a plugin that makes it seriously easy to respect referential integrity rules from the database in the model.

There is a second use for plugins - Monkey Patching! Basically you can use a plugin to modify the core in a way that can used for test purposes. Maybe the feature needs some more work before it can be added to the core. Or in my case - maybe there is a bug in the core and you don’t want to have to switch to Rails Edge to get it fixed.

Enter FixPgTimestamp Plugin. (Be gentle this is the very first time I’ve actually released any ruby out into the world. The code is mainly based on a simple post in the Rails bug system from mat@absolight.fr.I just bundled it up into a nice simple plugin.)

Basically this plugin fixes the problem with created_at date caching that currently effects the main version of Rails. To use it all you have to do is install it into your vendor/plugins directory and it will handle the rest. The best part is that when Rails 1.1 comes out and this fix is no longer needed you can simply delete the plugin and you won’t have to change any of your code. All in all pretty cool!

I didn’t really understand the power and usefulness of plugins until just a few days ago - and it turns out I learned about them just in the nick of time.

Update

Thanks to some help from Rich Olson I got a plugin server up and running. Now you can :

script/plugin install http://source.economysizegeek.com/svnroot/rails/pluginsfix_pg_timestamp

If you would prefer to keep up using an externals setting
script/plugin install -x http://source.economysizegeek.com/svnroot/rails/plugins/fix_pg_timestamp


Postie - 0.9.9.3.2 BUGFIX

Don’t you hate it when you leave in debug code on accident - I know I do.

The new version can be found Here (< - Now you can always go to http://postie.economysizegeek.com if you want to get to postie.)
.


    You are currently browsing the Economy Size Geek weblog archives for March, 2006.
    Previous Entries »
    Categories
    Archives

    .