liveandlearn

RUBYOPT - How it works

November 20th, 2008

The RUBYOPT environment variable is a handy way to specify the options that will be pased to ruby without having to type them in all the time.

According to the ruby source code you can customize your ruby interpreter by specifying any of the following arguments in RUBYOPT: ‘I’, ‘d’, ‘v’, ‘w’, ‘W’, ‘r’, or ‘K’.

For example to always require rubygems when you run ruby simply put export RUBYOPT="-r rubygems" into your .profile or .bashrc. But wait there’s more. According to the rubygems documentation you can simply set RUBYOPT=”rubygems”, how does that work? Well this trick depends on a couple of things. First RUBYOPT does not actually require you to put a dash in front of your arguments. This kind of makes sense when you think about it since you have already declared the value of RUBYOPT to be options to the ruby interpreter by virtue of the fact that they are in a special environment variable. However, on the command line dashes are required to distinguish between arguments and files to run. So what does not requiring dashes leave us? Well you could expand RUBYOPT=”rubygems” to RUBYOPT=”-r ubygems”. This brings us to the second part of the trick. Rubygems ships with a file named ubygems.rb that has this line require 'rubygems'. All of this adds up to some “command line syntactic sugar” allowing you to simply specify RUBYOPT=”rubygems”.

Yesterday I encountered a strange error that caused me to dig into how RUBYOPT is used; here it is for the benefit of those googling: no such file to load -- ubygem (LoadError). The problem is that RUBYOPT was set to “rubygem” when it should have been set to “rubygems”, or “-r rubygems”, or, “rrubygems”, or “-r ubygems”… you get the idea.

Posted in Ruby | Comments Off

Sake task for mod_rails (aka phusion passenger)

June 17th, 2008

So phusion passenger for local development is the bomb! Sake bomb is also fairly cool in it’s own right. I got tired of manually updating httpd.conf and /etc/hosts to add new phusion passenger virtual hosts so I wrote a little sake script to do the work for me. Want it?

sudo gem install sake && \
sake -i http://pastie.caboo.se/216294.txt

Update: I am now using the passenger preference pane instead of my sake script.

Posted in Rails | 2 Comments »

In the beginning there was chaos…

June 7th, 2008

…afterwards there was a shelf and slightly less chaos.

As you can see I still have some cleaning up to do, but I think the shelf is a huge improvement. According to the time-stamps off the before and after photos it took me approximately 7 hours to complete this project.

Posted in Organization | 1 Comment »

Yummy Breakfast :-)

June 4th, 2008

Monday Emily fixed me a very yummy breakfast. Redi-whip+pancake+strawberries == good!

Posted in Personal | No Comments »

In 2040…

May 20th, 2008

The other day I started thinking (shocking I know) about how old my child will be and how old I will be. I wrote down the following on the front of an envelope:

Year	2008	2010	2015	2020	2030	2040
Me	28	30	35	40	50	60
Baby	0	2	7	12	22	32

Posted in Personal | No Comments »

Use aptitude not apt-get and friends

May 6th, 2008

From Aaron Toponce’s blog:

Aptitude is just superior to apt-get in every way, shape, and form. Better dependency handling. Better curses application. Better options. ONE tool. Better stdout formatting. The list goes on and on. I see constantly, on forums, IRC and email, the use of apt-get. We need to better educate our brethren and sisters about the proper use of tools, and show them the enlightened way of aptitude. I’ve been using aptitude since I first learned about it, a[n]d will continue to do so the remainder of my Debian/Ubuntu days.

Posted in Uncategorized | No Comments »

How to ban evil robots

April 3rd, 2008

I saw a tip on how to automate banning of evil robots posted by ironclad here.

It got me thinking about how to automate detecting and banning of robots for rails. It seems like all that is required is a combination of a DISALLOW /email_addresses/ line in robots.txt and something to send all requests for /email_addresses to the bit bucket.

This should be easy enough to do in apache with a rewrite rule:

RewriteRule ^/email_addresses - [F,L]

And I imagine nginx can do something very similar.

However this only takes care of robots that expressly do what they should not. In order to ban abusive robots by user agent or ip address you could use something like the following:

RewriteCond %{REMOTE_ADDR} “^63.148.99.2(2[4-9]|[3-4][0-9]|5[0-5])$” [OR] # Cyveillance spybot
RewriteCond %{HTTP_USER_AGENT} EmailSiphon [NC]
RewriteRule .* - [F,L]

Posted in Uncategorized | No Comments »

Keep monit running on ubuntu > 6.10

March 6th, 2008

Who is monitoring monit? Well normally init is (or could be), but newer versions of ubuntu (read feisty) don’t really use init, they use upstart. If you want to keep monit running with upstart try my monit upstart job.

Posted in Uncategorized | No Comments »

Mongrel + monit (really mongrel_cluster + monit)

February 12th, 2008

According to Ezra the best way to train your mongrels with monit is through mongrel_cluster. Mongrel_cluster is a more reliable way to start and stop your mongrels than issuing straight mongrel_rails commands.

What if you have a bunch of mongrels? It would be a pain to have to write out the monit configuration for each one, and what happens when you need to change your mongrel config? You would have to remember to hand update all your monit entries too. Enter mongrel_monit a script to generate a monit file based on your mongrel config.

Posted in Uncategorized | No Comments »

Leopard, FreeNAS and ISCSI

January 3rd, 2008

I installed Leopard a few days ago, and in preparation I created a bootable backup of my system using the excellent Carbon Copy Cloner. While fairly simple to do, the downside is that I have to have a physical drive present with enough space. What would be really handy/cool is if I had a storage server that I could allocate and export a new drive from over the network. Then the storage server can worry about making those bytes available and redundant.

Well there is some good news and some bad news (for now). The good news is that this is exactly what ISCSI does and it is really simple to setup with FreeNAS. The bad news is that I couldn’t get everything working on Leopard, even though I could with windows.

A quick definition of ISCSI from wikipedia:

iSCSI is a protocol that allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers. It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

As you can see there are two pieces to ISCSI, the targets or storage devices and the initiators or clients. Using the FreeNAS live cd I was able to quickly setup a storage server and export an ISCSI target. I was then able to use the microsoft ISCSI initiator to connect to the target and format the disk. Pretty cool! I now have access to raw disk space that is managed completely by FreeNAS and available anywhere I have a network connection.

Now onto the sad part. I tried to connect to the same ISCSI target from my Mac using the only freely available ISCSI initiator from Apple globalSAN. The initial connection worked fine, but when I opened DiskUtility and attempted to format the drive, DiskUtility became unresponsive and never finished formatting the drive. I don’t know if this is a limitation of globalSAN or of DiskUtility, but I hope that there will be a working solution for free ISCSI on the Mac in the near future.

Posted in Uncategorized | 1 Comment »

liveandlearn

RUBYOPT - How it works

Sake task for mod_rails (aka phusion passenger)

In the beginning there was chaos…

Yummy Breakfast :-)

In 2040…

Use aptitude not apt-get and friends

How to ban evil robots

Keep monit running on ubuntu > 6.10

Mongrel + monit (really mongrel_cluster + monit)

Leopard, FreeNAS and ISCSI

Archives

Categories

Links

Meta