Backups go in DocumentRoot

[pearcec]

A backup gets created an put in the DocumentRoot. Every time you run cap deploy after a failed attempt it keep rolling in the prior backup. This seems sloppy. Seems capistrano-ash isn't well though through on the issue of managing backups.

[grafikchaos]

your right. it is a bit sloppy and assumes to much that the backup process went through without failure. the thought process behind it was:

• dump and gzip the database to the current release's document root so it's easy to find if you need to do a rollback and restore (which hasn't been implemented yet)
• make a temporary copy of the current release document root (file level with all symlinks) to the <deploy_to>/backups/tmp directory
• create a tarball of the recent temp backup and copy the tarball to <deploy_to>/backups path
• cleanup temporary copies

Right now, we prefer humans to do restores over automating tasks but that is in the works.