Running Upgrade.php with an externally hosted MySQL database failing on backup step

[ntbutler-nbcs]

Hi all.

We have our MySQL instance running on a separate server. When we go to run the upgrade.php file we have it bomb out at the backup database step, which is because the mysqldump binary is not installed on the local webserver.

Should the upgrade.php file be updated for that step to handle this situation? Or, is there an environment variable that I've missed that could be used to effectively skip this step?

At this stage, we have just been commenting out those lines of the upgrade.php file before we begin, and running dumps/snapshots on the separate server anyway, but if there is an existing method that we should be following for this setup then we'd obviously like to make sure we are following that.

Cheers!

[snipe]

You'd need to install the mysqldump binary on the local server - it can talk to outside databases. https://stackoverflow.com/questions/44583004/how-to-config-spatie-laravel-backup-when-datadase-was-on-another-machine

Stack Overflow

How to config spatie/laravel-backup when datadase was on another machine

I try to use spatie/laravel-backup, In my local I can config 'dump_binary_path' => '/usr/local/mysql/bin'.

But in my PROD server database was on another machine. My application call database s...