everzet/capifony — pull request #112 by jeremykendall (2012-04-12 11:40:41+00:00)
Title: Removes --password flag from pg_dump

The --password flag for pg_dump doesn't accept a password as a parameter like mysql_dump does. cap database:dump:local and cap database:dump:remote fail in their current state. Removing the --password flag allows pg_dump to succeed, but only if there is a ~/.pgpass file in place (see [http://www.postgresql.org/docs/9.1/static/libpq-pgpass.html](http://www.postgresql.org/docs/9.1/static/libpq-pgpass.html)). That means a ~/.pgpass file will need to exist on the local dev box and each box where cap will deploy.

The ~/.pgpass requirement should probably be enforced with a warning message if the file doesn't exist, but that's well beyond my current ruby capabilities.