| | |
|---|
| | |
|
|---|
| | | *SINCE 0.6.0*
|
|---|
| | |
|
|---|
| | | A Gitblit federation is a mechanism to clone repositories and keep them in sync from one Gitblit instance to another. Federation can be used for automated backup of your repositories or may be used to initially clone groups of repositories to developer workstations. If you are/were a Subversion user you might think of this as [svn-sync](http://svnbook.red-bean.com/en/1.5/svn.ref.svnsync.html), but better.
|
|---|
| | | A Gitblit federation is a mechanism to clone repositories and keep them in sync from one Gitblit instance to another. Federation can be used to maintain a mirror of your Gitblit instance, to aggregate repositories from developer workstations, or to initially clone groups of repositories to developer workstations. If you are/were a Subversion user you might think of this as [svn-sync](http://svnbook.red-bean.com/en/1.5/svn.ref.svnsync.html), but better.
|
|---|
| | |
|
|---|
| | | If your Gitblit instance allows federation and it is properly registered with another Gitblit instance, each of the *non-excluded* repositories of your Gitblit instance can be mirrored, in their entirety, to the pulling Gitblit instance. You may optionally allow pulling of user accounts and backup of server settings.
|
|---|
| | |
|
|---|
| | | The federation feature should be considered a security backdoor and enabled or disabled as appropriate for your installation.<br/>
|
|---|
| | | Please review all the documentation to understand how it works and its limitations.
|
|---|
| | |
|
|---|
| | | 
|
|---|
| | |
|
|---|
| | | ### Origin Gitblit Instance Requirements
|
|---|
| | |
|
|---|
| | |
|---|
| | |
|
|---|
| | | #### (Nearly) Perfect Mirror Example
|
|---|
| | |
|
|---|
| | | 
|
|---|
| | |
|
|---|
| | | This assumes that the *token* is the *ALL* token from the origin gitblit instance.
|
|---|
| | |
|
|---|
| | | The repositories, example1_users.properties, and example1_gitblit.properties will be put in *git.repositoriesFolder* and the origin user accounts will be merged into the local user accounts, including passwords and all roles. The Gitblit instance will also send a status acknowledgment to the origin Gitblit instance at the end of the pull operation. The status report will include the state of each repository pull (EXCLUDED, SKIPPED, NOCHANGE, PULLED, MIRRORED). This way the origin Gitblit instance can monitor the health of its mirrors.
|
|---|
