Weave Code
Redis Manager Laravel Package
encore/redis-manager
Encore Redis Manager is a Laravel package that simplifies managing Redis connections and data from your application. Configure stores, work with keys, and handle Redis operations through a clean, developer-friendly workflow.
Integrates your Laravel application with a redis manager
Frequently asked questions about Redis Manager
- How do I install encore/redis-manager in a Laravel application?
- Install it with composer require encore/redis-manager, then publish the package config if you need to customize connections or routes. On Laravel 5.5 and newer, package auto-discovery registers the service provider automatically unless you suppress it. Expect Composer conflicts on modern Laravel and PHP versions because the last release dates to 2018.
- Does encore/redis-manager support Laravel 9, 10, or 11 and PHP 8.2?
- The last release is from April 2018 and targets the Laravel 5.5/5.6 and PHP 7.1/7.2 era, so Composer will likely reject Laravel 9, 10, or 11 and PHP 8.2+ on illuminate/support or predis constraints. Using --ignore-platform-reqs is not a real fix outside a sandbox. The practical options are a constraint override, an internal fork with updated constraints, or choosing another tool.
- Is encore/redis-manager safe to run in production?
- No. The package exposes routes that can read and delete Redis keys, and its only access control is whatever middleware you attach. Default-on route registration in production is a data-loss and data-exfiltration risk, so treat it as development and staging tooling only.
- How do I disable or protect the redis-manager routes in Laravel?
- You can suppress package auto-discovery with extra.laravel.dont-discover or register the provider conditionally, then load the routes only in local or staging environments. Also wrap the routes in your own auth middleware and confirm the package does not register them unconditionally. Check the production route list to be certain.
- Does encore/redis-manager use my Laravel Redis connections or its own config?
- The package ships a publishable config and reads and writes through a Redis connection rather than coupling to Eloquent, queues, or cache. Whether it honors Laravel named connections or opens its own connection is not clearly documented, so verify against your config before pointing it at shared Redis. Do not assume cluster, sentinel, TLS, or Redis 6 ACL username support.
- Which destructive Redis commands does the encore/redis-manager UI expose?
- The UI is built to inspect and manipulate keys, so expect per-key deletes and likely FLUSHDB-style operations, with KEYS-based traversal a real possibility. There is no documented Gate or policy hook, only middleware, and destructive commands do not appear to be guarded. Never point it at a Redis instance that holds cache, queue, or session data other services depend on.
- Does encore/redis-manager use SCAN or KEYS to browse Redis keys?
- The documentation does not state whether keyspace traversal uses SCAN or KEYS, and there is no documented pagination or key-count cap. KEYS blocks Redis because it is single-threaded, so on a large instance it can stall every client. Inspect the source or your fork before using it against anything sizable.
- Can I install encore/redis-manager as a Composer require-dev dependency?
- Yes, and that is the recommended approach. Declare it under require-dev and keep it out of production images, which removes most of the security and blast-radius risk. Auto-discovery still registers it in local and CI environments, so guard the routes there too.
- What are the alternatives to encore/redis-manager for browsing Redis in Laravel?
- redis-cli, RedisInsight, and bastion-hosted Redis UIs cover the same key-browsing use case without adding an abandoned dependency to your app. Because encore/redis-manager has no schema or persistent state, the exit path is cheap: remove the Composer package and its routes. Many teams build a small custom dashboard on Laravel's Redis facade if they need app-specific views.
- Is encore/redis-manager still maintained, and does it support Redis 6 ACL or cluster?
- It has had no release since 2018, no CVE response, and no PHP 8 compatibility work, so adoption means permanent ownership. Cluster, sentinel, TLS, and Redis 6 ACL usernames are not documented as supported. If you keep it, plan an internal fork pinned to a commit with a security patch backlog item.
Weaver
How can I help you explore Laravel packages today?