git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Multiple clients accessing git over NFS

From
KSKhawaja Shams <kshams@usc.edu>
Date
Nov 14, 2010, 21:24 UTC
Message-ID
<AANLkTimyFkVFAw4s2fiWKZFPvnx15K6U6GbxmRgznx7Z@mail.gmail.com>
  Is it a recommended practice to share a repository over NFS, where
multiple clients can be pushing changes simultaneously?  In our
production environment, we have a Git repository setup behind
git-http-backend. We would like to place multiple Apache servers
behind a load balancer to maximize availability and performance.
Before we proceed, we wanted to check to see if this practice has a
potential to cause repository corruption. If there are other ways
others have solved this problem, we would be very interested in
learning about those as well. Thank you.
Next: Greg Troxel
Message 1 of 10 in “Multiple clients accessing git over NFS”
  1. Khawaja ShamsNov 14, 2010
  2. Greg TroxelNov 14, 2010
  3. Khawaja ShamsNov 14, 2010
  4. Jonathan NiederNov 15, 2010
  5. Jan HudecNov 15, 2010
  6. Drew NorthupNov 15, 2010
  7. J. Bruce FieldsNov 15, 2010
  8. Sitaram ChamartyNov 15, 2010
  9. AlexNov 16, 2010
  10. Greg TroxelNov 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.