Re: Working Copy on Network / Usage of multiple users
On Sat, Jan 19, 2013 at 7:42 AM, Karl Heinz Marbaise wrote: > > so after thinking about the concept... > it does not make sense to go further with a shared working copies on a > network drive there are too many issues (of course, cause SVN is not made > for such things)..so i will drop the idea... > Thanks for clearing up... > > > >> >> Have you considered other solutions? For example, the ASF CMS maintains >> one working copy per project, and uses zfs copy-on-write clones to fork >> off a per-user working copy for each user (even concurrent users) who >> works on that working copy. >> >> https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm >> > Does this solutions supports having different working copies per user which > can access them or are these working copies on a per project base? What > about locking of files in the working copy (svn:needs-lock) etc. ? How could > they be accessed ? > > Furthermore i have started to think about WebDav (after a hint of a > colleague of mine) might be a solution on Windows, but i don't know how > WebDav behave if two people working on the same file and saving the file? > What about conflicts? What about locking of files ? What problem are you trying to solve? Normally everyone checks out their own separate copy and then is free to commit/update on their own schedule and you can figure out how to fix conflicts after the fact if you don't communicate well enough to avoid them. It does consume a lot of disk space but that is usually a cheap commodity and if not you can trade off deleting workspaces after use and doing a fresh checkout when needed again. -- Les Mikesell lesmikes...@gmail.com
Re: Working Copy on Network / Usage of multiple users
Karl Heinz Marbaise wrote on Sat, Jan 19, 2013 at 14:42:30 +0100: > Hi, > >> Have you considered other solutions? For example, the ASF CMS maintains >> one working copy per project, and uses zfs copy-on-write clones to fork >> off a per-user working copy for each user (even concurrent users) who >> works on that working copy. >> >> https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm >> > Does this solutions supports having different working copies per user > which can access them or are these working copies on a per project base? > What about locking of files in the working copy (svn:needs-lock) etc. ? > How could they be accessed ? > The key part of the solution is creating working copies by creating copy-on-write forks of a "master" working copy (kept pristine at all times --- zfs floating tags, anyone?). For example, you could configure sudoers(5) to let any of your users run 'zfs clone /tank/mywc /tank/$USERNAME/$1'. Then the answers would be: - One or more working copies per user - Supported - local filesystem (or whatever you've hooked it to: webdav, scp/sftp, ...) Does that make sense ?
Re: Working Copy on Network / Usage of multiple users
Hi, > You'll need to think about permissions: when wc.db is rewritten, or a new .svn/pristine/ file created, would user2 have permissions to replace or unlink it (respectively)? Authz would be a concern too, if the two users' read accesses differ. (the code should DTRT --- it's no different than the server revoking some read access in a one-user scenario) Can someone give more detailed information if the above assumption is right or wrong ? I assume it's right... so after thinking about the concept... it does not make sense to go further with a shared working copies on a network drive there are too many issues (of course, cause SVN is not made for such things)..so i will drop the idea... Thanks for clearing up... Have you considered other solutions? For example, the ASF CMS maintains one working copy per project, and uses zfs copy-on-write clones to fork off a per-user working copy for each user (even concurrent users) who works on that working copy. https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm Does this solutions supports having different working copies per user which can access them or are these working copies on a per project base? What about locking of files in the working copy (svn:needs-lock) etc. ? How could they be accessed ? Furthermore i have started to think about WebDav (after a hint of a colleague of mine) might be a solution on Windows, but i don't know how WebDav behave if two people working on the same file and saving the file? What about conflicts? What about locking of files ? Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de
Re: Working Copy on Network / Usage of multiple users
Karl Heinz Marbaise wrote on Thu, Dec 27, 2012 at 16:03:55 +0100: > Network: working-copy-1 > User 1 accesses working-copy-1 and changes some files and will checkin > those changes. > > User 2 accesses working-copy-1 and changes some files and will checkin > those changes. > etc. > > My knowledge is that if those accesses to the above working copy can be > handled strictly sequential it might work but i'm not 100% sure..(may be > someone can give more detailed informations).. > You'll need to think about permissions: when wc.db is rewritten, or a new .svn/pristine/ file created, would user2 have permissions to replace or unlink it (respectively)? Authz would be a concern too, if the two users' read accesses differ. (the code should DTRT --- it's no different than the server revoking some read access in a one-user scenario) > Can someone give more detailed information if the above assumption is > right or wrong ? I assume it's right... Have you considered other solutions? For example, the ASF CMS maintains one working copy per project, and uses zfs copy-on-write clones to fork off a per-user working copy for each user (even concurrent users) who works on that working copy. https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm
Re: Working Copy on Network / Usage of multiple users
On 2012-12-27 16:03, Karl Heinz Marbaise wrote: > Hi, > > i just want to check my assumption by the user/dev community. > > I have the following scenario. > > From a central SVN server there should be done checkouts (different working > copies) on a network drive. > The working copies will be accessed from different users which means a thing > like this: > > Network: working-copy-1 > User 1 accesses working-copy-1 and changes some files and will checkin those > changes. > > User 2 accesses working-copy-1 and changes some files and will checkin those > changes. > etc. > > My knowledge is that if those accesses to the above working copy can be > handled strictly sequential it might work but i'm not 100% sure..(may be > someone can give more detailed informations).. > > Apart from that I expect failures if a working copy will be accessed in > parallel from different users at the same time on the network based on the > pristine-copy information and other meta-data which is stored in the .svn > folder (SQLite database etc.). > > Can someone give more detailed information if the above assumption is right > or wrong ? I assume it's right... > > Many thanks in advance. > Kind regards > Karl-Heinz Marbaise I'm not sure if I got your scenarios right ... - the working-copy-1 is located on a network share which is mounted by other users in read/write mode - user 1 - user N has mounted the working copy and modifies files there, so this changes are direct transparent to all others without "svn update" - user 2 --" same as user 1 "-- My question for this scenario is then more in the direction from which location in the working copy will user1/2 commit/update? Or is someone the svn master who updates/commits the changes? About the wc.db, even on a network share the database should be locked exclusive for write, so no other can do update/commits at the same time. I expect for this scenario more failures in the way how a single file will be locked during the work (two users are working on the same file, in worst case with notepad that does not lock the file and does not recognize changes) -- Regards, olli
Working Copy on Network / Usage of multiple users
Hi, i just want to check my assumption by the user/dev community. I have the following scenario. From a central SVN server there should be done checkouts (different working copies) on a network drive. The working copies will be accessed from different users which means a thing like this: Network: working-copy-1 User 1 accesses working-copy-1 and changes some files and will checkin those changes. User 2 accesses working-copy-1 and changes some files and will checkin those changes. etc. My knowledge is that if those accesses to the above working copy can be handled strictly sequential it might work but i'm not 100% sure..(may be someone can give more detailed informations).. Apart from that I expect failures if a working copy will be accessed in parallel from different users at the same time on the network based on the pristine-copy information and other meta-data which is stored in the .svn folder (SQLite database etc.). Can someone give more detailed information if the above assumption is right or wrong ? I assume it's right... Many thanks in advance. Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de
