Questions about federation
107 views
Skip to first unread message
E Guervos
May 9, 2012, 4:53:28 AM5/9/12
to gitblit
Hi James.
My Giblit:
GO 0.9.3
My O.S:
Linux - Centos 5
-- Questions: --
1.- Is there any way to skip certificate verification when working
over ssl ?
2.- And no less important. After removal of the frozen - How can we
push a federated mirrored (without conflicts)?
3.- I have observed, that after accepting a proposal which tokem is
ALL (in which one of my origin is federated as mirrored), my origin
back to me server as a mirrored feferated, ??, ¡such as does an echo!.
That would it solve the directive federationStrategy=EXCLUDED ?
Again, thanks for your time
My Giblit:
GO 0.9.3
My O.S:
Linux - Centos 5
-- Questions: --
1.- Is there any way to skip certificate verification when working
over ssl ?
2.- And no less important. After removal of the frozen - How can we
push a federated mirrored (without conflicts)?
3.- I have observed, that after accepting a proposal which tokem is
ALL (in which one of my origin is federated as mirrored), my origin
back to me server as a mirrored feferated, ??, ¡such as does an echo!.
That would it solve the directive federationStrategy=EXCLUDED ?
Again, thanks for your time
James Moger
May 9, 2012, 7:48:30 AM5/9/12
to git...@googlegroups.com
1. The Federation RPC protocol disregards SSL verification failures. After transferring the Gitblit metadata, standard Git communications are used to clone/pull using Gitblit's git servlet. The pulling Gitblit/FedClient will need http.sslVerify=false in the global Git config. Now if you still have an SSL problem it will be because the certificate hostname does not match the hostname in your clone/pull url. Unfortunately, this is an annoying upstream bug in JGit.
2. This is beyond the scope of what I wrote. Federation has no conflict resolution. If you need to push to a mirrored repository, I would suggest committing to new branches that are guaranteed NOT to exist in the origin Gitblit instance.
3. I don't quite understand what you wrote.
-J
2. This is beyond the scope of what I wrote. Federation has no conflict resolution. If you need to push to a mirrored repository, I would suggest committing to new branches that are guaranteed NOT to exist in the origin Gitblit instance.
3. I don't quite understand what you wrote.
-J
E Guervos
May 9, 2012, 9:33:53 AM5/9/12
to gitblit
Point 3, a best explanation:
a) I have a repo, and send a proposal to a remote gitblit server (the
tokem mine it's custom), this remote makes a mirror of this.
b) The remote does a pull from my repo.
c) Then the remote sends me a proposal whose tokem (him) it's ALL.
d) I accept it, and I come back my repo as a repo him, when really is
a mirror that has from mine.
e) As is logical, I erase it, cos' I have it.
You understand me now?
a) I have a repo, and send a proposal to a remote gitblit server (the
tokem mine it's custom), this remote makes a mirror of this.
b) The remote does a pull from my repo.
c) Then the remote sends me a proposal whose tokem (him) it's ALL.
d) I accept it, and I come back my repo as a repo him, when really is
a mirror that has from mine.
e) As is logical, I erase it, cos' I have it.
You understand me now?
James Moger
May 9, 2012, 9:41:15 AM5/9/12
to git...@googlegroups.com
I think I do.
A is your Gitblit.
B is the remote Gitblit.
B is pulling A, but you also have A pulling B so this is bidirectional.
Things you could do...
On B you could configure your federation set to not include this repo.
On B you could set this repo to NOT_FEDERATED.
On A you could specify an exclusion for this repo.
(federation.fromB.exclude = somerepo.git)
-J
A is your Gitblit.
B is the remote Gitblit.
B is pulling A, but you also have A pulling B so this is bidirectional.
Things you could do...
On B you could configure your federation set to not include this repo.
On B you could set this repo to NOT_FEDERATED.
On A you could specify an exclusion for this repo.
(federation.fromB.exclude = somerepo.git)
-J
E Guervos
May 9, 2012, 10:04:06 AM5/9/12
to gitblit
Yes that do it. (On B, I set the repo from A how to NOT_FEDERATED)
Thk.
Thk.
Reply all
Reply to author
Forward
0 new messages