There’s a critical bug in Typo 5.0 that has forced us to retire Typo 5.0.x from Rubyforge until we find out what really happens.
It seems that, under certain still undefined cicumstances, when runnin SQLite, which is at the same time our default installer and Ruby on Rails 2.0 database, Typo just erases itself with its parent directory.
We’re actively working on this issue, even on new year’s eve, trying first to find out if it’s a Typo or Rails VS SQLite matter. Be sure we’ll release a 5.0.2 version fixing everything as soon as possible. We apologise for the inconvenience.
This also happens using mysql as your database. Has happened twice!