Thus said David Mason on Tue, 13 Aug 2013 13:12:47 -0400: > All I want is for my users to say: > > fossil clone ssh://remote/proj.fossil clone.fossil > > [snip] > > It appears that I can do that (possibly with a small auxiliary script) > with the changes that Andy is working on.
You can probably do it today, without any of the changes I've been working on as long as the Unix permissions on the Fossils are such that it allows write access from multiple individual Unix accounts. I have not tested it this way, but in theory it should work. I don't know if Fossil will automatically create new Fossil users as you grant Unix users permission to the Fossils, or if you'll have to add them as you go. In your example above, who is the user that will login to SSH? Obviously it will be your shell account that you are using on your local machine (unless you have overidden it in ~/.ssh/config). But what if you want to have just a single SSH account to house all of your Fossils for a team? To clarify, the changes I've been making will: 1) make Fossil less dependent on the shell environment; to avoid problems as were mentioned in this thread, and others: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg09936.html 2) make it easier for to restrict access via SSH keys and aggregate all the Fossils under one account. 3) make it more flexible for SSH environments in general. Hopefully I can accomplish this. :-) Andy -- TAI64 timestamp: 40000000520a8135 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
