A couple of my websites were begun on my Alienware PC (running Windows, of course). Later I moved development to my Mac. But tonight I started using Phusion Passenger to deploy my Rails web applications in Apache 2. An elegant and revolutionary solution for the Rails community, no doubt! But there was a problem when I finished the migration and started up the websites under the new Passenger setup. A lot of files failed to load. All HTML loaded fine, as did many images. But some images failed to load, and the stylesheets too. Hmm... Why would some images load and some not, if they're in the same directory?

It turns out that the images added when I was developing on Windows were not loading, but the images added from my Mac loaded fine. Why? Permissions! When you copy Windows files to a Linux server or to a Mac, the permissions look like this:

-rw------- 1 geek geek 781 2009-01-31 01:23 accept.png

-rw------- 1 geek geek 789 2009-01-31 01:23 bell.png

-rw------- 1 geek geek 882 2009-01-31 01:23 clock.png

Not good enough for Apache to serve them to site visitors. Mac and Linux copy the files with more friendly permissions, like this:

-rw-r--r-- 1 geek geek   652 2009-05-03 14:13 feed-icon.gif

-rwxr-xr-x 1 geek geek 18173 2009-05-03 14:13 GeekSkillz_logo1.png

-rwxr-xr-x 1 geek geek  3214 2009-05-03 14:13 IK_guy_footer.jpg

So, a simple chmod on the files fixed the problem and all files started getting served again.

To me, this is a testament to how well Mac and Linux work together, since Mac OS X is really a highly customized distro of Linux. Develop on Mac, deploy on Linux, and win! Or just develop on Linux and deploy on Linux, I guess.

Why does Windows set the permissions like that? Another way that Windows tries to babysit its users? Assume users have the worst intentions and implement strict restrictions?

Anyway, what am I rambling about? Rails development on Mac for a Ubuntu server with Apache and Passenger are awesome? Abandoning Windows has made me fitter, happier and more productive? Yeah, I guess those are good conclusions.

Blah blah blah. I'm going to bed. Good night, blog.

Cell Stage

This phase is a gorgeous re-interpretation of Pac-Man. It is elegant, fluid, and calming. I suspect that this is where the game's inspiration started and ended. "Wouldn't it be neat if you could play a multi-cellular organism and play through it's evolution?" Yes it would be neat, and it is! Huzzah! As I played this stage, I marveled at how my creature gradually grew in size and shape with each generation, and the fuzzy gigantic organisms in the depths of the primordial ooze gradually focused and joined my creature's food chain. Then a few minutes later, my creature was the gigantic organism and they were the nuggets I was snacking on, soon to be too small to even see. Checking my creature's history at the end of the stage, I saw that almost 7 billion years had passed. This stage truly captures the essence of evolution, and more importantly, it's a fun game. Still, it's Pac-Man and the novelty wears off after half an hour.

Creature Stage

Still grinning from the cell stage, I enjoyed the creature stage. I got the most enjoyment after having my creatures "mate" so that I could change my species. With each generation, I improved the look of my species so that I liked it more as I played. In a sense, my satisfaction with my species increased a bit with each generation. This stage didn't feel so much like evolution as it did intelligent design. *shudder* My choices while playing had little impact on the evolution of my species. Playing the creature stage means doing only a few things: picking up species customizations from the ground, killing other species, and making friends with other species. That's it. Killing and befriending are really the same action with different animations. As for the evolution, couldn't the developers have thought of something more creative than picking up parts to evolve your species? I don't think Darwin suggested that birds got their wings by finding them on a beach, or that reptiles scooped up their brains from a pond.

Still, I enjoyed this stage well enough. It plays like a prototype of World of Warcraft, except without any cool features. Hmm... did I really enjoy it? Maybe I was just excited to be playing Spore, with the promise of the space stage still to come. *sigh*

Tribal Stage

Having reached the tribal stage, the hours spent customizing my species were made irrelevant and my highly evolved brain began to tell me that Spore might suck. Still, the space stage will be great! Right?

In the tribal stage, my creatures were too small to make out any of the details that made my species so cool! (If I do say so myself.) It plays like a real-time strategy game, like the original Warcraft games. But I played the first Warcraft RTS, and it had a lot more going for it than Spore's tribal stage. Spore has stripped down the RTS formula to its most basic elements, so that you end up with a stage that isn't fun, isn't challenging, and abandons everything you've done in the game so far. This stage is where the train wreck that is Spore begins. Spore has officially gone off the rails here.

On the bright side, I unlocked the achievement for beating the tribal stage in less than an hour. I hated it almost immediately, so I got through it as fast as possible. It's so simple, I can't see how anyone could spend more than an hour, or why they would want to.

Civilization Stage

The civilization stage is awful, awful, awful. And I had to spend more than an hour on it. I don't even want to write about it.

What's worse is that elements of this stage carry forward into the space stage. Arranging buildings in your little cities is a chore you will need to perform repeatedly in the space stage after every attack (see later). There's nothing fun about designing and arranging the idiotic cities in Spore. Even on the highest graphic settings, they are a blurry, blobby mess. And I still can't see my wonderful species, as they're being blocked by blurry buildings! Bah! Frustration rises!

Space Stage

And here's where the train wreck appears in all its horrifying glory. I played the space stage for three evenings (about 10 hours), because I just couldn't look away. "Is it really this terrible?" Yes, I've concluded that it is. Here's are some of my problems with it:

1. Endless Attacks: My colonies are always under attack, and I have never had more than 2 colonies at a time! Every 5 minutes a popup message tells me I need to save a colony. I decided to just ignore the attacks, which turned out to be a bad strategy. There's no time to explore space between all the attacks. While I investigate a planet to see if I want to colonize it, it's a sure thing that I'll be called away to deal with yet another attack. How is that supposed to be fun?

2. I want to explore! Following on number 1, I don't know how I'm supposed to explore space if I am kept busy with unprovoked wars and pirates. Can't I just have time to explore space and colonize planets for a while?

3. My ship won't defend itself outside of planets. My allies' ships will defend me, but there's no way to use my own ship's weapons in space. Why? Will I need to buy an expansion pack for this feature? Will I care?

4. Micromanagement of colonies: Each city on each planet needs to have its buildings plopped down inside a circle with connected lines that I guess is supposed to be a mini-game... It's annoying. Whenever a colony is invaded (every 5 minutes), buildings get destroyed. But I don't know which ones, so I need to check each city and replace what I think is missing. There's no shortcut for doing this, so I need to drag and drop each building again and again and again. While I'm doing this, it's possible that another attack will start somewhere else.

5. Space is crowded. It seems that the developers assume that space is filled with intelligent life. All the systems around me were quickly colonized by alien species, so I need to travel far away to find uninhabited systems. While searching, attacks are happening back home. Are you getting the picture yet?

6. Where's the sandbox? In marketing for the game, the space stage was promoted as a huge sandbox for you to play in. But this sandbox is the kind that throws sand in your eyes and kicks you in the groin repeatedly! It hurts! The sandbox hurts! Make it stop! I don't have any freedom to do anything creative or interesting in the space stage. It hates me, and I hate it.

The space stage, more than any other part of the game, is so disappointing it's maddening. How could Maxis have made it so irritating? Did the playtesters actually enjoy it, or were they simply ignored?

I'm not sure that I can play Spore anymore. If there's a patch that somehow fixes the space stage, then I'll give it another try. Or maybe some talented modders make some changes. I want to play it because the idea of Spore is alluring. I want the game that was supposed to be Spore!

If I find out how to make the space stage fun, I'll be sure to write a post about it. If you know what I'm doing wrong, please leave a comment! I would like to give Spore a second chance and start enjoying it. But for now, I'm completely disappointed.

Macintosh:geekblog me$ rake db:migrate --trace

(in /Users/me/rails/geekblog)

** Invoke db:migrate (first_time)

** Invoke environment (first_time)

** Execute environment

** has_many_polymorphs: rails environment detected

** has_many_polymorphs: preloading parent model Tag

** has_many_polymorphs: preloading parent model Tag

** Execute db:migrate

rake aborted!

You have a nil object when you didn't expect it!

The error occurred while evaluating nil.info

/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb:421:in `migrate'

/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb:420:in `each'

/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb:420:in `migrate'

/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb:357:in `up'

/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb:340:in `migrate'

/Library/Ruby/Gems/1.8/gems/rails-2.1.0/lib/tasks/databases.rake:99

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:508:in `invoke_with_call_chain'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `invoke_with_call_chain'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:494:in `invoke'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1931:in `invoke_task'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `each'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1903:in `top_level'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1881:in `run'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1878:in `run'

/Library/Ruby/Gems/1.8/gems/rake-0.8.1/bin/rake:31

/usr/bin/rake:19:in `load'

/usr/bin/rake:19

On line 421 of /Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/migration.rb, we find this:

Base.logger.info "Migrating to #{migration} (#{migration.version})"

At this point, Base.logger is always null (nil) in all my Rails projects, at versions 1.2 and 2.1, on Mac and Windows, in development and production environments. I don't know why... But the fix is simple. Change the above line so that it checks to see if the logger is null (which it should probably be doing):

Base.logger.info "Migrating to #{migration} (#{migration.version})" unless Base.logger.nil?

Since this "bug" has persisted for years, I assume this is a problem that others are not hitting. Logging works in my development and production environments, so logger should not be null in this case.

*shrug*

Life goes on.

Anyone else hitting this problem with rake db:migrate? Let me know so we can bond and so on.