Setting Up and Managing Replication

Setting up Replication in ProGet is straightforward, but the settings and structure of repositories make configuring it a little different to Artifactory.

In this article, we’ll look at setting up Replication in ProGet in a similar way to your Artifactory instance, and the different types of replication available.

Replication in ProGet

Users with an Enterprise license can set up Replication in ProGet between two instances. In ProGet, it’s feeds that are replicated. Push and Pull replication is supported, as well as single and multi-push replication. ProGet also allows you to Mirror Content, where a feed will both push and pull to ensure it’s synchronized.

Multi-push replication involves a Hub and Spoke configuration, where the source server acts as the “Hub”, and destination/edge servers are the “Spokes.”

Setting this up can be done following our guide on How to set up replication to edge locations.

Setting up Replication

Replication is set up in ProGet through the UI. It can also be done with the ProGet API.

Replication is configured in one of two ways, as Edge Locations or Federated Development.

Edge Locations

Edge locations use the Hub and Spoke model to easily distribute content to other servers. Setting this up involves configuring your hub and spoke servers, which can be done by following our guide.

There is also a specialized Edge Edition which has some additional features/dashboards that are specialized for edge computing and a licensing model designed to scale.

Federated Development

Federated Development allows software to be developed at multiple sites with multiple teams.

To set this up you’ll need to configure incoming and outgoing replication feeds, which you can learn more about in our guide for this.

Replication Scheduling

With Artifactory your replication is based on either a schedule or events, but in ProGet it’s performed automatically. If you need to do “one-off” replications, you can use ProGet’s Feed Migrators.

In ProGet replication status can be monitored from the Dashboard, a better alternative to JFrog’s script recommendations, as it saves time, simplifies tasks, and consolidates data in one place.

You can also use ProGet’s Health API to return the current replication status.

Conclusion

ProGet replication allows you to push and pull, and mirror content to keep everything synchronized, either through single or multi-push replication using hub and spoke servers.

Replication is set up easily through either the UI or API, and allows you to configure everything for either Edge Locations or Federated Development.

The next step is to plan for keeping your data secure, which we cover in the following article on Backup and Restore.