Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
We are interested in implementing a lazy caching artifactory server (slave)
on a different network than the primary server (master). We began with a
remote snapshot repository configuration on the slave and noticed that the
yum repo metadata was synced the first time and the yum install command
worked on a linux node pointing to the slave. However, after subsequent
snapshot updates on the master (mvn deploy), these packages to not appear to
be available to the linux client. We believe this is likely because the
yum/rpm metadata is not synced.
I then attempted to configure replication of the repodata (yum/rpm metadata)
where the slave would periodically pull from the master. Unfortunately, the
following message was presented:
Replication between same-license servers is not supported.
Do you have a best practice for this setup?
View this message in context: http://forums.jfrog.org/artifactory-pro-lazy-cache-with-yum-tp7578993.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.