In previous versions of Capistrano, the database file was created in …/shared/db, and a simlink created in …/current/db to point to the actual database file. This allowed for database contents to survive re-deployments. I see this functionality has been removed – or at least I can’t find it in the current system. And the book no longer discusses this matter as far as I can tell.
What is the current recommended way to deploy a project without losing the current database contents?