cincproject/rubygems-cinc-sh repository overview

rubygems.cinc.sh

The gem server behind https://rubygems.cinc.sh⁠, where Cinc publishes its rebuilt gems (omnibus, omnibus-software, cinc-auditor and the rest). Geminabox⁠ on Ruby 3.4 (Alpine), served by puma on port 9292, with an unrestricted API key for push and yank, optional gem-scoped API keys so a project can publish only its own gems, and Basic Auth for the web UI. In production it sits behind nginx, which caches gem files and index metadata.

• Source: https://gitlab.com/cinc-project/rubygems.cinc.sh⁠
• Tickets/Issues: https://gitlab.com/cinc-project/rubygems.cinc.sh/-/issues⁠
• Slack: #community-distros⁠

How do I use this image?

The repository's compose.yml runs this image together with nginx and is the supported way to deploy it. Standalone:

docker run -d -p 9292:9292 -v geminabox-data:/var/geminabox-data \
  -e API_KEY=... -e ADMIN_USER=... -e ADMIN_PASSWORD=... \
  cincproject/rubygems-cinc-sh
gem push my-gem-1.0.0.gem --host http://localhost:9292 --key API_KEY

Configuration is entirely through environment variables (API_KEY, API_KEYS for scoped keys as a JSON map of key to gem names, ADMIN_USER, ADMIN_PASSWORD, GEMINABOX_ALLOW_REPLACE); see the repository README for details. Gems are stored under /var/geminabox-data.

Tags

• latest only, amd64.

How is this image built?

• Built and published by the repository's CI pipeline with docker buildx bake. The Dockerfile is here⁠.