Welcome and thanks for giving Fossil a try!
Thanks & my pleasure.
Although our experience with Fossil is still limited, we're all finding
Fossil very easy to like! [:-)]
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.
Yes.
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 Fossilusers
will clone to, but where the clones reside is distributed and
dynamically handled by the redirection service?
Precisely.
So, the redirection service does nothing but help people reach other. If a
POST or GET reaches the service, the only thing it really does is redirect
the client (here: Fossil) to the actual IP address of the intended person.
Definitely an interesting setup.
Thanks [;-)].
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.
Exactly. We wanted to circumvent that. In a way, different people are "in
charge" of different parts of the software. So, I guess in that respect it
also felt more natural to distribute the "master repositories" (in a
manner of speaking).
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.
Unfortunately, it's segfaulting. So I have no error messages whatsoever I
can share with people...
Ashwin.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
