I have used WF with multiple sites on 4 app servers with no problems. I did not have the plugins folder mounted but mainly because the guys who mad the themes had code that relied on certain plugins being available. If our NFS mount went down, so did the site. I prefer that anything the site needs to load be local.
Anyway, I’m not sure why you might be having an issue this way unless you are having multiple sites (not servers or subdomains of a multisite installation) trying to access the same plugin.
tim
Hi,
I don’t know how much this will help, but I have a small clustered environment (a load balancer, two web servers, and a database server). I host a copy of the files on each server, and sync every minute using cron using a tool called unison. Many tools could do that. You could also try something that will automatically sync files as they’re modified like glusterfs, but I have had bad experiences with glusterfs in particular slowing down my site massively so that’s why I’m just using a sync solution like unison.
-Michael.
Duplicating the plugins folder for a single WP instance doesn’t make sense to us. If our WP install can’t access the NFS mount where not only our plugins, but uploads folder and other various files are symlinked – our site would go down.
We have it setup this way for an automated deployment process and we don’t keep plugins in our repo.
I think we’ve traced the issue to a cache file referenced in /lib/wfConfig.php Line 514.
If this was made to be an option in the Admin, we could set it to a relative local path. Or even provide an override in wp-config.php.
Thoughts?
Sorry, this slipped past me. Can you send details of this (and your proposed fix) to samples [at] wordfence.com? You can reference this thread but it would be really helpful if you explained what you were trying to do or the problem you are having in as much detail as possible, and the code you think is the problem, your fix, and why you think that would help. I’ll send it over to the dev team.
I can’t promise every suggestion we get is included in a release but every suggestion is carefully considered and evaluated for community benefit, resource usage, etc. We take every suggestion very seriously and appreciate our users.
I’ll resolve this for now and wait for your email.
tim
