How to Point RubyGems at Chainsaw

Beginner 15 minutes Developers / DevOps Engineers Getting Started

Configure Bundler and your Gemfile to install Ruby gems through your Chainsaw proxy.

Overview

Point RubyGems at your Chainsaw instance so every bundle install passes through the firewall. This page covers Bundler mirror configuration and the Gemfile source directive.

Replace chain305.com with your own Chainsaw deployment host and swap CLIENT_ID / CLIENT_SECRET for credentials issued from the Access page in the dashboard. The @default segment is the org slug — confirm yours under Settings → Organization → Slug. Legacy non-org-scoped URLs return HTTP 400 with error CHW-4314.

Prerequisites

  • A running Chainsaw instance (see Tutorial 01)
  • Client credentials (Client ID and Secret)
  • Ruby, RubyGems, and Bundler installed

Clear Local Caches (First-Time Setup)

rm -rf vendor/bundle Gemfile.lock
gem cleanup
bundle cache --no-cache

Bundler Configuration

bundle config mirror.https://rubygems.org https://chain305.com/chainproxy/repository/@default/rubygems-official/
bundle config chain305.com/chainproxy/repository/@default/rubygems-official/ CLIENT_ID:CLIENT_SECRET

Gemfile

source "https://chain305.com/chainproxy/repository/@default/rubygems-official/"

Verify

Run bundle install, then confirm with chainsaw doctor verify-hook and the Traffic page in the dashboard.

Next Steps