The rpmcache is simply that, a cache, the actual rpms are stored in a
mapped hash based on disk format that Artifactory tracks in its database,
it doesn't use a flat file format because that is inefficient to the levels
of scale it can handle. If you access your server at your repo URL you will
see the repodata folder and if you configure it as a repo on a server it
will function perfectly. From what I've gathered the only use of the
rpmcache folder is allowing them to quickly incrementally index a
repository without having to do a full query against every rpm. Trust the
process and read the documentation, the 'Set me up' buttons in the UI are
amazingly helpful.
On May 20, 2016 12:12 AM, "user_01_01" <[email protected]> wrote:
> I thought that with Artifactory with Yum integration I could use the
> Artifactory UI to create local yum repos, which in turn would write
> directories local to my server and then deploy, again, through the
> Artifactory UI, rpms, to my local repos, which, at the server level, would
> actually upload rpms into those directories that Artifactory previously
> created. Then, I thought if I pointed my artifactory.repo baseurl at
> basically
> /var/opt/jfrog/artifactory/some-repo-I-created-in-the-artifactory-UI, that
> when I ran "yum install whatever", it would call out to artifactory.repo,
> hit the baseurl and then install "whatever.rpm". Where am I going wrong?
> Because all that's happening is when I create a local repo through the UI
> it's like it just caches everything somewhere, stores the actual rpm in
> /var/opt/jfrog/artifactory/data/.rpmcache and that's it. So where am I
> going wrong?
>
>
>
> --
> View this message in context:
> http://forums.jfrog.org/Yum-does-Artifactory-do-more-than-cache-tp7581026.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
