diff options
| author |  divB <divB@web> | 2014-07-08 07:41:59 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-07-08 07:41:59 +0000 |
| commit | d2b8c8663b3c486c02e400534e777f9aff45d881 (patch) | |
| tree | 3a67f2888b39dc990109d395665e93263524c705 | |
| parent | 07f28797444133cd5c2618f9c43d1317b0142206 (diff) | |
| -rw-r--r-- | doc/forum/Best_approach_for_central_sharing_and_multiple_users.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Best_approach_for_central_sharing_and_multiple_users.mdwn b/doc/forum/Best_approach_for_central_sharing_and_multiple_users.mdwn new file mode 100644 index 000000000..6fc104cb8 --- /dev/null +++ b/doc/forum/Best_approach_for_central_sharing_and_multiple_users.mdwn @@ -0,0 +1,8 @@ +Just a quick question: Can anyone recomment me a good to handle a centralized repository which is used by different users? + +Requirements: must work in direct mode on both sides, server is Linux, clients are Windows and operated by 2 different users. + +- Should the repository create bare or not? +- Must the repository created on the server or can it also be "pushed" from one client to the server (via SSH on the server)? +- Is there a better way for data transfer than SSH (WebDAV as in SVN)? I am still struggling with an elegant way to handle public keys in windows +- What is the best way to not only keep meta data in sync but also the data each of the users has checked out? |