Currently the README stipulates that if --magento-project is specified, the --magento-db must be specified as well. Based on the setup scripts currently implemented however, this requirement does not appear to be there for a technical implementation reason, so I would like to propose lifting the restriction. This will support setting up a Mage2Click based environment using a local source directory without having a database artifact already present.
With this change, either parameter may be specified independently of the other allowing the setup process to either run setup:install or import the database from the provided dump file, even when a local project source directory is given, allowing for greater flexibility during the setup process.
Example use case would be setting up a Magento Commerce project from scratch using composer meta packages, where there is most likely no database artifact available for import during setup:
Currently the README stipulates that if
--magento-project
is specified, the--magento-db
must be specified as well. Based on the setup scripts currently implemented however, this requirement does not appear to be there for a technical implementation reason, so I would like to propose lifting the restriction. This will support setting up a Mage2Click based environment using a local source directory without having a database artifact already present.With this change, either parameter may be specified independently of the other allowing the setup process to either run
setup:install
or import the database from the provided dump file, even when a local project source directory is given, allowing for greater flexibility during the setup process.Example use case would be setting up a Magento Commerce project from scratch using composer meta packages, where there is most likely no database artifact available for import during setup: