For the work we're doing for the backup command in issue #8, we need to be able to leverage drush commands from spark on production environments where we're not using docker.
Note: we do have a way to run drush commands locally and in the containers, but currently the code is hardcoded to always run in the containers, via the DrushCommand::setIsContainer.
This needs to be refactored to auto-detect if the php docker container is available, and if not, fallback to running drush locally.
For the work we're doing for the backup command in issue #8, we need to be able to leverage drush commands from spark on production environments where we're not using docker.
Note: we do have a way to run drush commands locally and in the containers, but currently the code is hardcoded to always run in the containers, via the
DrushCommand::setIsContainer.This needs to be refactored to auto-detect if the
phpdocker container is available, and if not, fallback to running drush locally.