Closed ottok closed 6 years ago
This is caused by missing wrapper wp-pull-production-db
. Added in f584c0a, rebuild in progress.
@ottok If you'd like to test the fix, seravo/wordpress-beta
has now the latest image (version 20180605.0.3) with missing wrapper added.
This has been released as seravo/wordpress.
Cannot test yet:
$ vagrant box update
==> mariadb-box: Checking for updates to 'seravo/wordpress-beta'
mariadb-box: Latest installed version: 20180605.0.2
mariadb-box: Version constraints: >= 20160718.15.0122
mariadb-box: Provider: virtualbox
==> mariadb-box: Box 'seravo/wordpress-beta' (v20180605.0.2) is running the latest version.
I confirm this works now. I did spot the message ==> redacted-box: mysqldump: Can't create/write to file 'pre-production-pull-backup-1528705315.sql' (Errcode: 13)
but I don't know if it matters for now.
In context:
==> redacted-box: entering site container... /usr/local/bin/wp-pull-production-db
==> redacted-box: |----------------------------------------------------------------------------|
==> redacted-box: | Welcome to Seravo.com! |
==> redacted-box: | Unauthorized use is forbidden. All connections are monitored and recorded. |
==> redacted-box: |----------------------------------------------------------------------------|
==> redacted-box: Saving backup of current development database in /data/db/pre-production-pull-backup.sql...
==> redacted-box: mysqldump: Can't create/write to file 'pre-production-pull-backup-1528705315.sql' (Errcode: 13)
==> redacted-box: Define new and old siteurl for later search-replacing...
It works once Vagrant is fully up and running, but the command initiated by the
vagrant up
wizard does not seem to find the command in the right path: