DOC-7168 Add a connect page for redis-rb (Ruby)

[andy-stark-redis]

Adds a connect page for redis-rb, the only Ruby client without one, and links it from ruby/_index.md. Part of DOC-7168 (epic DOC-7164). The Rust page is in a separate PR.

What's on the page

• Basic connection: an ACL user, a URL (credentials must be URL-encoded), and a Unix socket
• Redis Cluster, using the separate redis-clustering gem, including reads from replicas
• Redis Sentinel: separate credentials for the Sentinels and the data nodes, and connecting to a replica
• TLS, including mutual TLS (client certificates)
• Connection pools with the connection_pool gem
• Timeouts and reconnection
• Protocol: RESP3 is the default as of 6.0

Client-side caching, smart client handoffs and Entra ID authentication aren't supported by redis-rb, so the page leaves them out.

How the examples were tested

All 21 code blocks ran against local servers:

• a standalone server with an ACL user and a Unix socket
• TLS servers with the client certificate optional, and with it required
• a cluster of 3 primaries and 3 replicas
• Sentinel

The test copies differed from the page only in ports, hosts, passwords, certificate paths and key names.

Component	Version
redis	6.0.0
redis-client	0.30.1
redis-clustering	6.0.0
redis-cluster-client	0.16.7
connection_pool	3.0.2
Ruby	4.0.6
Redis	7.2.7

redis-client 0.30.1 and redis-cluster-client 0.16.7 are the exact versions that redis 6.0.0 and redis-clustering 6.0.0 pin.

The gem install lines weren't run, because RubyGems wasn't reachable from the test environment.

Please review these two caveats

Both are based on what we measured, not on the client's own documentation:

1. Lost writes after a Sentinel failover. We forced two failovers. After each one, redis-rb kept writing to the old primary until Sentinel turned it into a replica. The old primary then discarded those writes, even though the client had received a success reply for each one: 22 and 20 writes were lost. This matches the caveats added to the other clients' pages in DOC-7167 Add Redis Sentinel connection examples to client connect pages #4229.
2. Writes can run twice. redis-rb retries once by default. We dropped a reply after the server had already run an INCR, and the default retry ran the command a second time. The page suggests reconnect_attempts: 0 or without_reconnect for commands that aren't safe to repeat.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no application or infrastructure code.

Overview
Adds a dedicated Connect to the server page for redis-rb, bringing Ruby in line with the other client guides.

The new connect.md documents how to connect with ACL users, redis:// / unix:// URLs (including URL-encoded credentials), Redis Cluster via redis-clustering, Sentinel (separate sentinel vs data credentials, replica reads, and failover write-loss behavior), TLS / mutual TLS, connection_pool, timeouts and reconnect retries (including non-idempotent command caveats), and default RESP3 in redis-rb 6.0.

The Ruby landing page (_index.md) now points readers to that page for cluster, Sentinel, and TLS setup.

^{Reviewed by Cursor Bugbot for commit 678cc01. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

DOC-7168

[github-actions]

🧠 Redis Memory

Found 5 related items from repository history (5 new this commit):

• PR — DOC-7167 Add Redis Sentinel connection examples to client connect pages 🆕

  Adds a "Connect to Redis Sentinel" section to each client connect page, right after the cluster section. Fixes DOC-7167(https://redislabs.

• PR — DOC-7165 Add a connection URLs page covering all client libraries 🆕

  Adds a Connection URLs page to the client libraries section, covering the `

• Commit — DOC-7167 Add Redis Sentinel connection examples to client connect pages 🆕

  DOC-7167 Add Redis Sentinel connection examples to client connect pages

• Commit — DOC-7165 Add a connection URLs page covering all client libraries 🆕

  DOC-7165 Add a connection URLs page covering all client libraries

• PR — DOC-6999: port alternative rate limiter algorithms to the other eight client pages 🆕

  Follow-up to docs: add fixed window, sliding window log, sliding window counter, and leaky bucket algorithms to redis-py rate limiter page #3788, which added four extra rate limiting algorithms to the redis-py page only. This ports them to the remaining eight client

Memory updated at 678cc01

[github-actions]

Staging links:
https://redis.io/docs/staging/DOC-7168/develop/clients/ruby/
https://redis.io/docs/staging/DOC-7168/develop/clients/ruby/connect/