Typo installation is about as friendly as a cornered rat

I think one of the reason's everyone's been hesitant to work on this bug is:

with no offense to the original author, but it's a crappy bug report. It's a nice "Mission Statement," but there's no nitty-gritty.

Maybe we need to spawn off a whole bunch of more bite-size bugs in the category "What needs to be done before you could do a "gem install typo""

Speaking as the original author here, nobody seems to be working on the bug is because Scott's dealing with it.

'gem install typo' sounds sexy, but where does that actually put the application? I don't think it makes a whole lot of sense. Not unless you want to provide a typo command that creates a fresh typo blog, a la the rails command.

I think it would be just as well to download and extract the tarball, and have a working typo with an existing empty sqlite3 database. The new user simply runs 'script/server -e production' (or maybe 'rake run' or something) and can get started on port 3000. This includes having a frozen rails in the download. Then the express dependencies would simply be ruby and the sqlite3 database driver.

As for making the leap from webrick to apache or lighttpd, I may be wrong (and would like to be wrong) but I think the best you can do there is provide or point to some excellent documentation.

The idea of a typo command similar to the rails command was the intention behind gem install typo.

And while it would be nice to be able to do ./script/server and have something running right off the bat, that would require a dependency on the sqlite3-ruby gem, and I personally would rather not force people to install the sqlite gem if they're not planning on using sqlite. Rails has built-in support for mysql (although you should install the gem anyway to vastly improve performance), but of course typo can't automagically detect available mysql databases.

What might be best is to have the proposed typo command accept arguments that tell it what database type and how to access it, and it would create the database and load the schema for you. Or something like that.

You have to edit config/database.yml in any case, and a fresh sqlite db is just a small file that can be autogenerated in the dist target. I see no disadvantage to a default sqlite setup.

setting this to blocker as it seems to be gating the release of 4.0

Fixed. The installer is now in the tree.