Support » Fixing WordPress » [Plugin: W3 Total Cache] w3tc config file on multi-server environments

  • I’m setting up a new multiple server environment for one of our wordpress sites.

    I ran across w3-total-cache-config.php, which appears to be the config file for w3tc. Now if these settings are store in a file (vs db) does that mean I’ll need to sync this file across all the servers (nfs, sync script, etc)?

    This is in the w3tc FAQ:
    “Is this plugin server cluster and load balancer friendly?
    Yes, built from the ground up with scale and current hosting paradigms in mind.”

    Seems like a file based config that I have to sync myself between servers isn’t exactly cluster/load-balancer friendly.



Viewing 2 replies - 1 through 2 (of 2 total)
  • Jason, we experienced a similar issue with replicating the w3tc settings across servers. We have a dedicated wp-admin server which is locked down via VPN which saves content and settings for the load balanced front end servers.

    We setup a frequent rsync of the w3-total-cache-config.php settings files (including /wp-content/w3tc/*) from our wp-admin server to the front end servers, it works pretty well.

    One of the advantages we have found with having the w3tc settings outside of the DB has been replicating them (via file upload) with our test servers which have different databases, its good to have the settings separate from content.

    Hope this helps


    @mald0r0r, there are lots of ways to build a cluster and deploy and application to it. Lots of people think it’s possible to scale MySQL by having settings file in it and it may not be obvious but it’s not. Lots of clusters use an NFS, even if they don’t applications can be deployed in such a way that files are copied to multiple application servers. If you actually want advice for your case, please ask a specific question after describing your deployment.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: W3 Total Cache] w3tc config file on multi-server environments’ is closed to new replies.