Geminabox

What it does

Audience

It provides private gem hosting for teams managing their own Ruby gems.checked 11 Oct 2026

Authentication

Authentication is left to the web server or Rack stack, and the README suggests Rack::Auth::Basic for basic authentication.checked 11 Oct 2026

Bundler integration

Bundler finds hosted gems through the compact index without client configuration.checked 11 Oct 2026

Dependency safety

The README recommends scoped Gemfile sources, which pin each gem to one source to guard against dependency confusion.checked 11 Oct 2026

Deployment

Geminabox runs as a Rack application and can be started with rackup or deployed with Rack servers such as Passenger, Puma, and Unicorn.checked 11 Oct 2026

Docker

The project documents running Geminabox in Docker and notes that a mounted data volume preserves gems when the container is replaced.checked 11 Oct 2026

Integrations

A gem-received hook can run custom code such as a team-chat notification, but the hook blocks upload processing unless slow work is made asynchronous.checked 11 Oct 2026

License

The GitHub repository identifies the project as MIT licensed.checked 11 Oct 2026

Proxy limitation

RubyGems proxy support was removed in version 4.0 because the dependency API it relied on was sunset and merged local and remote sources could invite dependency confusion.checked 11 Oct 2026

Purpose

Geminabox lets you host your own gems and push new gems to it like rubygems.org.checked 11 Oct 2026

Push and yank

Clients can push gems with the standard gemcutter push API or the gem inabox plugin, and yank gems with the gemcutter yank API.checked 11 Oct 2026

Ruby requirements

The README lists Ruby 3.0 or later and RubyGems 3.2.3 or later as system requirements.checked 11 Oct 2026

Security guidance

For a publicly accessible server, the setup example recommends Rack::Protection to help prevent XSS and CSRF vulnerabilities.checked 11 Oct 2026