Minimal Server API for Gem Installation?

[stefanvanburen]

I'm aware of the RubyGems API, but I'm wondering if there's a defined set of endpoints I'd need to provide so that someone could just install a gem by pointing at my server (think gem install -s <my-server> <gem>) - no searching, no publishing, no profiles, etc.

From a quick look, I'd assume I'd have to support:

• GET - /api/v1/gems/[GEM NAME].(json|yaml)
• GET - /api/v1/versions/[GEM NAME].(json|yaml)
• GET - /api/v1/versions/[GEM NAME]/latest.json (maybe?)

I'm also aware of the other Gem servers, but I'm not a rubyist, I'm not able to easily grok the code :-).

(Somewhat relatedly, does gem / bundler look at an index to determine what gems exist on a gem server? Or do they just do a lookup by [GEM NAME] to the above endpoints?)

[stefanvanburen]

I think I've somewhat answered my own index question: in the "setting up repo" section of "Using S3 as a gem source", it looks like some index files must be generated in order to use the bucket.