My Professional Blog

As we speak, I’m now probably 7 minutes into rebooting my Rails container. Why? Because all my apps went down and won’t restart and that’s the only thing I can think of to do. Why is it taking so long? Your guess is as good as mine.

They do seem to be able to keep my blog up, but even the initial admin page came up without a stylesheet. I’m not sure what’s going on over there, but something is definitely wrong. I’m not sure if I’m alone on this, but I’m definitely going to perform a Technorati search to see if anyone else is having trouble.

I am not running mission-critical apps here. Nor am I running high traffic sites. If I were, I’d be either losing money or losing credibility or both. If you have a site where either of those are concerns, I’m forced to recommend that you don’t host it at Media Temple. At least, not in the Rails containers. They clearly do not have that technology figured out yet.

10+ minutes and still rebooting the container.

I’d also like to add that support seems pretty spotty as well. Its likely that you’ll get a quick initial response, but it may not be well-considered or thorough. After you respond again, there’s a longer wait for the next reply. One of my tickets is on its fourth iteration and they finally directed me to a page full of support links. I don’t really call that “support”.

So it looks like this weekend I’ll be finding a new host for my Rails apps. Here’s hoping this post saves others some money. I have a reservation into Slicehost, but there’s a waiting list there. Looks like I may have to bite the bullet and pay more than I wanted to and use someone like RailsMachine.

Up after 20 minutes, but the container still shows its rebooting. Not acceptable.

I have subscribed to Why the Lucky Stiff’s Redhanded blog for quite some time, but lately I’ve been unable to fight through the distractions.  I present to you his latest performance.  Is anyone else wishing he’d kill the noise, so that we can all learn from him?

I’m pretty sure that I sound like a Father telling his kid to turn the music down…and so at least I am self-aware.

Its probably because I come from the Java world that I felt compelled to create an app configuration mechanism which enabled easy externalization of app properties.  This is not an Earth-shattering, whiz-bang plugin, so I’m not going to oversell it.  Quite simply, this plugin just enables you to put properties into an app.yml file and manage it nicely with Capistrano.  So maybe this’ll save you 10 minutes of coding.  Here goes:

FEATURE SUMMARY

This plugin provides for easy externalized configurization in a YML file:

• Common and environment-specific configuration contained in a single YML file.
• Capistrano task to preserve configuration file from release to release.

USAGE
Place configuration elements common to all environments in the common area as demonstrated below:

1
2
3

# Configuration for ALL environments.
common: &common
  app_name: your_app_name_here

Place environment-specific elements under appropriate environment as shown below:

1
2
3
4
5

# Configuration for PRODUCTION environment.
production:
  <<: *common
  google_api: some_long_api_key_here

To obtain the values from anywhere in your code, simply access the attributes of the environment like so:

1
2
3

puts AppConfig.app_name
puts AppConfig.google_api

DEPLOYMENT

To preserve the configuration values across releases, call the symlink_app_config task from within the after_update_code task.

1
2
3

task :after_update_code, :roles => :app do
  symlink_app_config
end

To update the app.yml file for the first time or for subsequent times, the task update_app_config can be used as below:

cap update_app_config

This takes the app.yml file from the config directory of the application and uploads it to the release path on the server.

You can get it here:

script/plugin install http://dev.billeisenhauer.com/svn/projects/plugins/appconfig

Hope someone finds this useful.

Today I woke up to find that every single one of my Rails apps hosted at Media Temple were down and would not restart.  I received no notifications whatsoever and am somewhat baffled as to why this is the case.

I am actively coding on one app, but the other two are pretty much unchanged.  As such, I don’t believe there’s anything that I’ve done to cause this.

I do have the 64MB container, so I know I’d be pushing the limits if they all were popular.  The fact is, I actually have only two of the three up at any given time, so I thought I could squeeze in within that smallish container.  Upgrading to the next bigger size is something that I have not wanted to do because I haven’t felt completely comfortable since Day One.

Anyone else have experiences to share with Media Temple?  I’m about to pack up my toys and go play somewhere else.  I was seduced by the Grid Container concept, but I am about ready to declare that it may not be ready for prime time — and its not like I’m doing much here either!

advrailsdallas_5

Originally uploaded by pragdave.

This past week I attended the Advanced Rails Studio in Dallas and had a fabulous time. The picture you see is from our lunch outside on Friday — I am in mid-gesture at the near table on the left.

If you have the opportunity to go to one of these studios, I think you’ll both benefit and enjoy it at the same time. The Rails Community is filled with a smart and optimistic bunch of people who are very fun to be around.

The Studio itself was run with amazing attention to detail. I can tell you that I was very well-fed and not just with bottom-feeding food, either. Kudos to Mike and Nicole for making the logistics so automatic.

Unlike my experience at the basic Studio back in January 2006, this one involved much more discussion and debate. Just imagine 40+ knowledgeable developers getting together to share experiences. Of course, there were class notes, but these served mostly as enablements for discussion. Often, the value of the section was not in the notes, but in the discussion.

I do find that I generally am well-versed in most of the content that I see in the course notes. With the number of Rails and Ruby books becoming available and the amount of blog activity its hard not to be informed these days. So for me, the value of the course was in the sharing and reinforcement that I know the latest practices and that I know any applicable heuristics.

Bottom line: highly recommended.

To the uninitiated, RIF means reduction in force.

On February 15th, Nokia announced that they would be reducing staff in their IT organization.  A total of 90 people globally were said to affected.  Finland was to be affected first, then the folks Stateside.  Apparently, there are complicated labor laws in Europe and so it took them a while to get to us in the States.

We had received little information until finally meeting invitations were received by all.  In those meetings you were to be told if you were staying or going.  I was told today that I was going.

I was prepared for this news, but still surprised.  In January, I received my best review yet, though all my reviews have always been better than average.  In addition, I’m on a team that already is short-handed and serves a business with aggressive goals.  I’m involved in two high-priority initiatives targeted for June 30th deployment.  The funny thing is, we just yesterday met to begin to explore who might back me up while I’m gone on my upcoming vacation.  In the end, no one really had the time, but we decided we’d explore it as the time grew closer.  So to me, this decision does not appear to be in harmony with business needs and competencies.  I am sure there will be some interesting fallout once our business partners learn that their goals may be affected by these cuts.

Quite frankly, this is a change for me that has been a long time coming, and though this is not necessarily on my terms, I am looking forward to what’s next.  I will make that the subject of some future blog entry as I figure it out.

Its fair to say that Nokia has some challenges ahead to right their ship.  Many of the points that I made in my Why IT Sucks post were inspired by some of my recent experiences there.  Based upon the feedback inspired by the Reddit readership who visited the entry, my experiences there are not unrepresentative of the industry as a whole.  But anyway, they really need to consider their management approach in both their business and technical areas.  We rarely saw our line or organizational management wandering the aisles or asking questions.  There are opportunities for them to get to know “the factory”, improve it, and be better equipped to manage and sell its services.  Without knowing its people or processes, its inevitable that each may go astray.

On the bright side, while at Nokia, I was able to supplement my Java skills and to be a part of bringing complex systems into being.  We introduced the Spring Framework to the company as well as other frameworks like the Acegi Framework for Security.  Not only did we introduce it, we built a federation of 20+ web apps that are happily deployed on a WebLogic Platform, but none of these apps use session beans or entity beans.  We introduced lightweight J2EE into the company successfully and we did so based upon our own initiative.  This is to say that we found the framework, we learned it without any formal training, and we deployed it successfully.  This is quite a feather in our caps.

I did introduce Ruby and Rails where I could, but quite honestly it just doesn’t appear to be taking hold.  Nokia is really a Java shop and they announced recently a desire to move to LAMP architectures.  I don’t disagree with LAMP architectures, but I think Ruby and Rails would enable cleaner application architectures to evolve.  I don’t think this was even considered because the idea of LAMP architectures came from Finland and there doesn’t appear to be too much awareness of Rails in Finland.  Apparently Jarkko isn’t spreading the word well enough. :)

To be fair to Nokia, they have at least been pretty fair with the termination process.  Some companies put you out on the street with little notice and with little regard to your financial situation.  Nokia has defined a transition period, where I will transition whatever I know and whatever I am involved in, followed by another period where I am not required to be onsite or carry any responsibilities.  The point of this period is to look for employment.  Thereafter, there is a lump sum severance which is reasonable given my 5-year tenure.  Suffice it to say, this is the best I’ve been treated and I am thankful.

So with that, its on to what’s next and I’m looking forward to the ride!