Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I wonder what the best choise is/practices are for a shared drive between multiple webservers. The same application needs to be employed on multiple webservers servers for load balancing considerations. I'd like to have the source of the application at one central place, just for the sake of management.

So, - are NFS, SSHFS and Samba all reasonable choises? - is it likely for me to require a local file cache per webserver, and this possible with all the different possibilities?

Thanks in advance.

share|improve this question

closed as primarily opinion-based by Rex, Ward, Falcon Momot, cole, Jenny D Dec 24 '13 at 20:32

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

I wouldn't put application code on a network mounted filesystem. Run that locally. Rsync, svn, git make having a centralized management location easy to push changes out. I believe it far preferable to have application code running from local disk, as opposed to over the network.

For all other assets, image files, videos, graphics, etc. I believe you'll find NFS an easy and cost effective solution. There are plenty of NAS devices at various price points and performance levels, and unless your requirements call for storage switches and fiber cards, you can do everything over plain CAT copper and your existing network infrastructure. Building your own basic NFS server is also quite feasible even for novices.

NFS drivers and packages exist for virtually every OS distribution and are usually quite reliable. And especially for your basic webserver.

Local file caching presents another layer of complexity, especially if you're writing to the NFS share, that I would avoid unless you absolutely need to maximize performance.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.