Bustikated

List of crap we’d like to talk about

• Camping / Merb / Rack
• PDF / Image Libs
• Config Mgmt / Cruise Control
• Passenger
• REST
• Attachment Plugins
• Mock / Stubs
• Testing frameworks
• Messaging Queues
• Search Index (Solr/Sphinx)
• Fixtures
• Javascript
• GIT / SVN
• Deployment / Capistrano / Vlad
• Thin Controllers / Fat Models / No Logic in Views
• Work process
• E-Commerce / Activemerchant
• BJ / Background DRB
• Charts & Graphs

I was looking at microformats for use in a current project, and decided that I’d like a way to export contact data as a vCard. A quick google search revealed this, which just happens to be by Derek Neighbors. It uses the VPIM library, which I found here.

Being the “There’s no way I’ll remember any of this later” person that I am, I tossed this into a pastie, and am blogging about it more for my benefit than yours.

I’ve updated the live WeeMap with the numerous minor changes in the last few days.

• Corrected email subjects
• User info bar (with username and logout link)
• Login redirects to Maps instead of Home
• Various tweaks

The BIGGEST change in this release is the addition of tag based filtering/searching.

And with that, I’m off to bed. Be sure to check back here or the lighthouse for support/feedback.

Oh, and I’ve created a topic on the WeeWar Tangler Group for the app as well. Trying to keep everyone up to date.

My simple little WeeWar maps app is live!

Check it out: WeeMap

DNS might still be updating, so check back if it’s down for you.

I’ve managed to get SVN & Warehouse somewhat up and running on my server, and now that he’s online, I’m trying to get everything 100%.

Right now, I’m testing the following post-commit hook in one of my repositories to see if it works. The directory names have been changed to match my server, but otherwise this is just the basic suggestion from the Warehouse FAQ.

#!/bin/sh
cd /Library/WebServer/Rails/warehouse-1.1.6
/usr/bin/rake warehouse:post_commit \
     RAILS_ENV=production \
     REPO_PATH=$1 \
     REVISION=$2

Inspired by a similar php solution found here, I decided to try and do this in Rails.

I quickly realized that something like this could be implemented as a plugin, in spite of it’s simplicity.

Google led me to this howto on creating generators, and following along with this and another of Urubatan’s guides, I was able to get a working plugin created.

Installation

As of right now, I do not have a public subversion repository. This should change within a week or two. The only way to install the plugin is to manually unzip it into your application’s vendor/plugin directory.

Get the zip here

This is my first plug-in, and was written more as a chance for me to explore plugin creation than out of necessity.

If you’re interested in creating your own plugin, you can read my notes by clicking ‘more’.

more

Ok. I’ve re-uploaded the gems. Still nothing. I switched over to development mode and CGI instead of fastCGI and finally started seeing error messages. Turns out GoDaddy is running old system GEMs, and needs to update.

The biggest problem here is that I’ve frozen my rails version to my app’s vendor/ directory. There should be nothing else (core Rails wise) that is needed to run my app. I’m not using any non-standard gems, and my plugins are all in the app itself.

For more details on the exact issue I’ve run up against, see this ticket

This ticket has been listed as ‘invalid’. Such a shame that the core developers disregard those of us who eek out a meager existence on shared servers.

Mostly for my benefit later, but maybe helpful to you other rails newbs: I always seem to not be able to find this quickly when I want to freeze mah gems. It isn’t that hard, I’m just that absent minded.

To lock in a specific version:

rake rails:freeze:edge TAG=rel_2-0-2

Ensure all your config files match:

rake rails:update:configs

To double check which version is actually being run by your app:

script/about

There’s a good how-to over at the RoR Wiki but I’m going to repost a quick & dirty reference here, mostly for my own benefit the next time I go through this.

The point is to ignore sensitive info in the database.yml file, and the ever-changing log & tmp directories. I’m no SVN guru, so feel free to point out flaws in this system.

more