[Pulp-list] Ruby gems mirror

[Ashby, Jason (IMS)]

Thanks Michael, that answers a bunch of questions.  If I find the time in the near future, I'll get to work on gem support. Thanks to the pulp team for making some great software.

On Oct 12, 2014, at 8:27 PM, Michael Hrivnak <mhrivnak at redhat.com> wrote:

Jason,

Pulp cannot manage ruby gems directly yet, but that would be a nice plugin to have. If you or anyone else is interested in making that happen (writing code), the core pulp team would be happy to help guide that effort.

Reading the blog post you linked to, my guess is that they packaged their gems as rpms and thus managed them as normal yum repos.

Michael

----- Original Message -----
From: "Jason Ashby (IMS)" <AshbyJ at imsweb.com>
To: pulp-list at redhat.com
Sent: Sunday, October 12, 2014 2:03:29 PM
Subject: [Pulp-list] Ruby gems mirror



Has anyone created a gems repo with pulp? I can’t seem to find info on what the actual mirror URL would be on rubygems.org. Any idea what url to sync from?



Rubygems want you to use their custom mirror setup tool, but I’d prefer to create all of my package mirrors with pulp whenever possible.



This blog post suggests it is possible: http://www.krisbuytaert.be/blog/ruby-gems-yum-repo



Thanks,

Jason



Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.

_______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

________________________________

Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.