-
Notifications
You must be signed in to change notification settings - Fork 29
Description
When attempting to clone or synchronize a website via a remote server using the ee site clone and ee site sync commands, if the site has been provisioned with a custom public-dir, the wp-config.php configuration file is overwritten by the source file, causing an error during the database import process.
This problem only occurs when the clone is performed from a remote server.
Evidence:
I performed the test on two servers, verifying that:
- They can communicate via SSH.
- The website to be cloned has a custom public directory.
- Monitoring of the ee.log file.
The log shows that the cloned site is attempting to write to the database using the wp-config.php file copied from the source, and not the newly created file.
Upon completion, it is described as a successfully created site, but the log indicates that the cloned site was deleted after a database connection failure.
Example Command:
sudo ee site clone root@192.168.100.20:custom-public.local .
Checking access to both sites
Creating site. This may take a while...
Syncing files
Syncing database
Exporting database from source
Copying database to destination
Importing database in destination
Error: Error while executing clone-import-db. closure: Unable to import database on destination. Please check for file system permissions and disk space.
Cleanup export file from source and destination
Success: Site cloned successfully.
You have to do these additional configurations manually (if required):
1. Update wp-config.php.
2. Add alias domains.