Thus said Chad Perrin on Sat, 10 Aug 2013 20:07:41 -0600: > > And then they can clone from there: > > > > fossil clone http://[email protected]:4444/project > > > > Thank you. This looks like it will probably suit our needs quite well > for the time being. I'll investigate further on my own at this point, > though if any more informative replies come through I'll of course > learn from them as well.
By the way, if you do it this way, all IP addresses logged with commits to your fossils will appear to come from 127.0.0.1 and not from the actual SSH client that is being used to access it. This may or may not be important to you. This is one of the things that I attempt to address with the SSH updates I've been making when using SSH URLS (e.g. ssh://) for cloning: http://www.fossil-scm.org/index.html/artifact/005796c0dd84551a454a51816ae3e591d79c1e1d?ln=1499-1515 Andy -- TAI64 timestamp: 40000000520723f3 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
