Don't install SQLlite on server start when it wasn't installed already - #176
Conversation
kozer
left a comment
There was a problem hiding this comment.
For some reason, I get the following error ( is happening in trunk as well ):
Error occurred in handler for 'createSite': Error: ENOENT: no such file or directory, copyfile '/home/wild/.config/Studio/server-files/sqlite-database-integration/db.copy' -> '/home/wild/Studio/my-true-website/wp-content/db.php'
Can you verify, this is not happening when you try to create a new site, by following the usual process?
I am not seeing that error and creating a new site works without issues for me. |
It seems that deleting |
|
Thank you for addressing this oversight! 🙇🏻 I added automated tests in #179, as I believe this nuance could easily be overlooked in the future. |

Related to https://github.com/Automattic/dotcom-forge/issues/7416
When a site is started (not created), we check if the currently installed version of the SQLite integration is outdated and then try to update it. In the case that the SQLite integration was not installed we only want to install it when there is no wp-config.php file present.
Proposed Changes
Testing Instructions
A quick way to run local MariaDB is by using docker with:
docker run --name local-mariadb -e MYSQL_ROOT_PASSWORD=password -e MYSQL_DATABASE=wordpress_db -e MYSQL_USER=wp_user -e MYSQL_PASSWORD=wp_password -p 3306:3306 -d mariadb:latestPre-merge Checklist