Setups for distributed teams very depending on your situation.
If your distributed teams all work in offices (or remotely connect to
a satellite office) then you would want a Nexus in each office. The
satellite offices would proxy against the repository manager in your
main office (this is where your artifacts would be deployed to)
On the other hand if you just have single office and a handful of
telecommuting developers then you just need a single Nexus install.
In both cases you need a main Nexus install that will define your
proxy and hosted repositories. All deployments would go to this Nexus.
Any satellite Nexus would just be used to proxy artifacts from your
main install.
On Oct 19, 2009, at 10:10 AM, Adrian C wrote:
>
> Hi,
>
> I am currently evaluation repository managers and since we have
> distributed
> teams this is a feature that we would like to use. Is this possible
> or I am
> missing the point - should proxies be used? I suppose my interest in
> this
> type of feature is that it kills two birds with one stone since I
> would
> expect the mirror to be a backup of the other instance?
>
> Thanks,
> Adrian
>
>
>
> Johan S wrote:
>>
>> Hi
>>
>> How do I setup and configure a mirror of my existing nexus server?
>> Would like to have a backup location if one of my servers goes down.
>> Is it possible, or should I make sure I always deploy artifacts to
>> both?
>>
>> Regards Johan
>>
>
>
> --
> View this message in context:
http://www.nabble.com/How-to-create-a-mirror-of-Nexus-on-another-server-tp21909881p25958982.html> Sent from the Nexus Maven Repository Manager Users List mailing list
> archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
nexus-user-unsubscribe@...
> For additional commands, e-mail:
nexus-user-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
nexus-user-unsubscribe@...
For additional commands, e-mail:
nexus-user-help@...