From 29d170e7a33586e512033e80de4711e22edc1f7b Mon Sep 17 00:00:00 2001 From: Brandur Date: Thu, 1 Oct 2026 15:34:19 -0500 Subject: [PATCH] Remove mentions of Redis driver from README I put together an experimental Redis driver to help benchmark against some Redis job queues, but I didn't include it in the repo here (yet? it might be kind of interesting I suppose). Traces of it were left in the main README, so strip them out of there. --- docs/README.md | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/docs/README.md b/docs/README.md index a4b7337..f499db1 100644 --- a/docs/README.md +++ b/docs/README.md @@ -738,30 +738,6 @@ client = River::Client.new(River::Driver::Sequel.new(DB)) Neither driver installs `pg` or `sqlite3`; the application chooses its adapter. -### Redis (experimental) - -Add `riverqueue-redis` to use Redis 7+ without either SQL adapter: - -```ruby -require "riverqueue-redis" - -pool = RedisClient.config(url: ENV.fetch("REDIS_URL")).new_pool(size: 10) -client = River::Client.new( - River::Driver::Redis.new(pool, prefix: "my_app", schema: "shared"), - config: River::Config.new( - queues: {ruby: 10}, - workers: River::Workers.new.add(SortWorker) - ) -).start -``` - -Ruby and Go's experimental `riverredisv9` driver can share the same namespace, -using identical job records, indexes, and ID allocation. Stop the client before -closing the pool. No migrations are needed. Redis-only transactions cannot be -atomic with application SQL writes; Rails integration and Pro's SQL-backed -features are not supported. See the [Redis driver guide](../driver/riverqueue-redis/README.md) -for durability requirements, compatibility, and other experimental limitations. - ## Testing For database-backed insertion assertions and synchronous worker tests, see