Thus said "Ashwin Hirschi" on Fri, 12 Dec 2014 00:29:57 +0100: > recently, my team started using Fossil. It took me a while to move our > existing code revisions to Fossil repositories. But it was worth it: > everyone's very pleased with what Fossil offers. So, I'm really glad > we made the jump.
Welcome and thanks for giving Fossil a try! > In this system, each team member has an associated, fixed URL. And > whenever a HTTP GET or POST request on such a URL occurs, the service > redirects the client to the actual (registered) IP address of the > corresponding member. Let me see if I understand this correctly... You have a bunch of team members, each hosting their own fossil repositories on their own unique (and sometimes changing) IP addresses. You have a redirection server in a central location that knows about these unique IPs and will dynamically update when the team member's IP address changes. Other team members will clone a given team member's fossil via the redirection service instead of the unique and changing IP address. So in essence, you've made a central location for where your Fossil users will clone to, but where the clones reside is distributed and dynamically handled by the redirection service? Definitely an interesting setup. You may have already considered the opposite: What if instead of the redirection, you just provided a Fossil hosting location? Each user could have their own project hosted in their own directory and Fossil could serve all of them from there? Then they would clone like: fossil clone http://redirection.server/user/project project Of course each user would probably need their own account on redirection.server to maintain their files for their account. > But oddly, 9 out of 10 "fossil commit" commands will fail. The > application crashes always seem to occur when Fossil tries to push the > changes to the remote repository. Sometimes the commited changes were > still transmitted, sometimes not... Any chance you can share the error that you're getting? Is it actually crashing (e.g. segfault) or is it just erroring out with an error? I suppose the latter question will be answered if you post an example. Thanks, Andy -- TAI64 timestamp: 40000000548a2fe4 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
