Thread

We have EE installed on two web servers which we use in production. Our designers can login and make updates at any time, but their updates that involve adding new files will only get written to the local filesystem of the application server they happen to be logged into at the time. Currently, we have a script which automatically commits these new files to a subversion repository every minute, and also pulls updates periodically. This isn’t an optimal solution for several reasons, not a small one being that the current_version file may get written to on both servers with different versions if we have two designers logged into two different application servers.

I’ve done some Googling, but haven’t found any recommendations from EE users about how to handle this issue. Any advice is greatly appreciated!

Thanks,

Eddie R.

I have a setup at Amazon running behind a load balancer and rather than replicating the files on all servers I simply have a centralized file server with a NFS export. I then mount this filesystem to each of the front end webservers. This way all the front end web servers all use the same file system so it doesn’t matter which you see when you login.

More details here assuming you are running Linux: http://how-to.linuxcareer.com/how-to-configure-nfs-on-linux