@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Use more precise language to describe what mirroring is
Summary: Fixes T10928. This behavior hasn't changed at all and this is what, e.g., `git push --mirror` means, and the other behavior isn't possible, but be more explicit about the inherent destructive potential of mirroring.
Test Plan: Read documentation.
Reviewers: chad, sascha-egerer
Reviewed By: sascha-egerer
Subscribers: sascha-egerer
Maniphest Tasks: T10928
Differential Revision: https://secure.phabricator.com/D15861
+11
-4
+11
-4
src/docs/user/userguide/diffusion_uris.diviner
+11
-4
src/docs/user/userguide/diffusion_uris.diviner
···
23
23
repository. This will create a read-only copy of the repository in Phabricator.
24
24
25
25
**Mirror Repositories**: Phabricator can publish any repository to mirrors,
26
-
updating the mirrors as changes are made to the repository. This works with
27
-
both local hosted repositories and remote repositories that Phabricator is
28
-
observing.
26
+
overwiting them with an exact copy of the repository that stays up to date as
27
+
the source changes. This works with both local repositories that Phabricator is
28
+
hosting and remote repositories that Phabricator is observing.
29
29
30
30
**Proxy Repositories**: If you are observing a repository, you can allow users
31
31
to read Phabricator's copy of the repository. Phabricator supports granular
···
102
102
NOTE: Mirroring is not supported in Subversion.
103
103
104
104
You can create a read-only mirror of an existing repository. Phabricator will
105
-
push all changes made to the repository to the mirror.
105
+
continuously publish the state of the source repository to the mirror, creating
106
+
an exact copy.
106
107
107
108
For example, if you have a repository hosted in Phabricator that you want to
108
109
mirror to GitHub, you can configure Phabricator to automatically maintain the
109
110
mirror. This is how the upstream repositories are set up.
111
+
112
+
The mirror copy must be read-only for users because any writes made to the
113
+
mirror will be undone when Phabricator updates it. The mirroring process copies
114
+
the entire repository state exactly, so the remote state will be completely
115
+
replaced with an exact copy of the source repository. This may remove or
116
+
destroy information. Normally, you should only mirror to an empty repository.
110
117
111
118
You can mirror any repository, even if Phabricator is only observing it and not
112
119
hosting it directly.