You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I keep previous dumps around to allow reloading (e.g. set :db_local_clean, false). With version 0.4, the dumps went into my projects ./db directory. With version 0.6, they were showing up in my project root. So I set :db_dump_dir as described in the README:
# configure location where the dump file should be created
set :db_dump_dir, "./db"
Now when I try to do a db:pull, I get a fatal error:
steven$ cap production db:pull
rvm 1.27.0 (latest) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]
ruby-2.3.1
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
Loading local database config
Local database: myproject_development
Please enter answer (Are you sure you want to erase your local database with server database (y)es, (n)o ? ): y
Loading local database config
Loading remote database config
00:00 db:local:sync
01 cd /home/deploy/apps/myproject/current && PGPASSWORD='secret_thingy' pg_dump -U deploy myproject_production --no-acl --…
✔ 01 deploy@myproject.com 0.195s
02 rm -f ./db/myproject_production_2017-01-05-084704.sql.bz2
✔ 02 deploy@myproject.com 0.042s
(Backtrace restricted to imported tasks)
cap aborted!
Net::SCP::Error: SCP did not finish successfully (1): scp: ./db/myproject_production_2017-01-05-084704.sql.bz2: No such file or directory
Tasks: TOP => db:pull => db:local:sync
(See full trace by running task with --trace)
The text was updated successfully, but these errors were encountered:
I keep previous dumps around to allow reloading (e.g.
set :db_local_clean, false
). With version 0.4, the dumps went into my projects./db
directory. With version 0.6, they were showing up in my project root. So I set:db_dump_dir
as described in the README:Now when I try to do a db:pull, I get a fatal error:
The text was updated successfully, but these errors were encountered: