Current process: I am installing EspoCRM with external MySQL database using the Azure Cloud. Currently I install EspoCRM on a virtual Machine, I dump the existing database, I create and connect this to a new external MySQL database (Azure). Then I configure the new database using the dumped database structure. This last step gives me a lot of errors of having default values (example: ERROR 1101 (42000) at line 4712: BLOB, TEXT, GEOMETRY or JSON column 'time_ranges' can't have a default value).
Remediation: the above step can be avoided if I can connect EspoCRM to an external database upon installation, instead of after installation.
Ideal process: when installing a new instance of EspoCRM, I can already point EspoCRM to an existing external database using the following settings as used in config-internal.php: 'host', 'dbname', 'user', 'password', 'actualDatabaseType' and 'actualDatabaseVersion'. This will avoid the unnessecary steps needed to dump the database and troubleshoot.
Current process: I am installing EspoCRM with external MySQL database using the Azure Cloud. Currently I install EspoCRM on a virtual Machine, I dump the existing database, I create and connect this to a new external MySQL database (Azure). Then I configure the new database using the dumped database structure. This last step gives me a lot of errors of having default values (example: ERROR 1101 (42000) at line 4712: BLOB, TEXT, GEOMETRY or JSON column 'time_ranges' can't have a default value).
Remediation: the above step can be avoided if I can connect EspoCRM to an external database upon installation, instead of after installation.
Ideal process: when installing a new instance of EspoCRM, I can already point EspoCRM to an existing external database using the following settings as used in config-internal.php: 'host', 'dbname', 'user', 'password', 'actualDatabaseType' and 'actualDatabaseVersion'. This will avoid the unnessecary steps needed to dump the database and troubleshoot.