Persist configuration to DB?
-
I am using W3TC with Docker and have noticed that the configuration disappears after restarting the container. Is there any way to persist this to the database so that when I deploy a new container I don’t have to reset this?
Exporting/importing works via the Admin Dashboard > Performance > General Settings, but that is after the container is deployed and running. This is rather impactful as instances need to scale out automatically.
I tried importing with WordPress CLI in entrypoint.sh with little luck and have reverted to copying /w3tc-config/master.php in the Dockerfile build process as a temporary kludge. This is less than ideal as we have multiple environments that use the same image with different databases/cdn connections and a high likelyhood of keys being held in source control.
Would it be possible to save this configuration to the database?
-
You could add
define( 'W3TC_CONFIG_DATABASE', true );anddefine( 'W3TC_CONFIG_DATABASE_TABLE', 'wp_options' );(replacewp_with your custom prefix) to yourwp-config.phpfile, which will store and load the settings in/from the database instead of a file.
The topic ‘Persist configuration to DB?’ is closed to new replies.
