Message-ID: <927902011.8405.1416705885871.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8404_251257259.1416705885871" ------=_Part_8404_251257259.1416705885871 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In a large corporate environment, i.e. multi-site or separate ap= plication devlopment, it may be advantageous to proxy internal repositories= .=20
To do so, add the a new mirror stanza (one for each repository to be mir= rored) and set the mirrorOf section to the same name as the repository bein= g mirrored, e.g. central, snapshots, inhouse, inhouse_snapshot, external_no= n_free, external_free=20 =20
If you have a multi-site environment you will need to configure your pro= xy so that it retrieve the artifacts over the network rather than from a lo= cal file system. You should have enough knowledge to be able to do this you= rself. (Author's note: I don't have such an environment, so if someone actu= ally does configure their environment like this and run's into gotcha's, pl= ease update this document)=20
Generally if your environment is not large and you have direct web acces= s to the internal repositories then there is no benefit from choosing to mi= rroring internal repositories.