- What is laravel-admin-ext/redis-manager and what does it do?
- It is an extension for encore/laravel-admin that adds a Redis management panel inside your existing Laravel admin dashboard. You can browse keys, inspect values and their types, edit or delete entries, and review cache contents through a web UI instead of redis-cli. It is an internal admin convenience layer, not a standalone Redis management product or a system of record.
- How do I install redis-manager in my Laravel admin panel?
- Install it with Composer alongside an existing laravel-admin installation, then register the extension so its routes and menu entries appear in the admin panel. Because the last release was in 2019, pin exact versions in composer.json and validate the install on a throwaway branch before touching shared environments. Do not add laravel-admin to a project solely to use this package.
- Which Laravel, PHP and laravel-admin versions does redis-manager support?
- The package metadata reflects a 2019-era stack, so the implied Laravel, PHP, laravel-admin and Redis client versions should be treated as a starting hypothesis rather than a guarantee. Confirm compatibility against your actual PHP, Laravel, laravel-admin and predis or phpredis combination with a short spike. Newer Laravel releases and stricter dependency constraints are the most likely sources of breakage.
- Is laravel-admin-ext/redis-manager still maintained?
- Signals point to it being effectively frozen: the last release was in 2019 and the package has zero dependents. Community support is best-effort at most, so plan for internal ownership, dependency pinning and a fork strategy if the tool becomes operationally useful. The permissive license makes forking straightforward but does not remove the security review work.
- Does redis-manager work with multiple Redis connections, such as separate cache, session and queue connections?
- The UI is commonly assumed to target a single default Redis connection, which may not match applications that split cache, sessions, queues and locks across separate connections or databases. Verify during your spike whether your connection topology is represented correctly before relying on it. If it is not, either fork to add connection switching or restrict the tool to the one connection it handles.
- Is it safe to use redis-manager in production?
- A Redis manager inside an admin panel can expose session data, queue payloads and application secrets, and it can issue destructive commands. Treat it as a high-value target: enforce admin roles, restrict it to non-production or read-only usage where possible, and check whether destructive actions are logged. If the package lacks read-only defaults and audit trails, add them by forking or keep it disabled in production.
- How does redis-manager handle large Redis databases and key scanning limits?
- Key browsing typically relies on Redis SCAN rather than KEYS, so behavior on large keyspaces depends on how the extension batches and limits results. Test against a representative dataset, because very large databases or long key names can make the UI slow or pagination awkward. Confirm scan limits and key naming and serialization assumptions actually match your application.
- How does authentication and authorization work for the Redis panel?
- The panel inherits laravel-admin's authentication and routing, so access control is only as strong as your existing admin guard and role setup. There is no separate Redis-level ACL layer described, meaning anyone with admin access may see whatever the configured Redis connection can read. Gate the extension behind roles and consider network-level restrictions on who can reach the admin panel at all.
- What are the alternatives to redis-manager for inspecting Redis in a Laravel app?
- If you do not already run laravel-admin, do not introduce it just for this package; prefer a small internal read-only Redis inspector or a dedicated managed Redis console. For day-to-day operations, hosted Redis provider consoles and tools such as RedisInsight cover inspection with better ACL and TLS support. Choose redis-manager only when laravel-admin is already your back office and the need is simple internal browsing.
- Does redis-manager support Redis ACLs, TLS and password-protected Redis?
- Modern Redis ACL users, TLS connections and multi-tenant patterns are not something this 2019-era extension is designed around, so support depends largely on what your Redis client and connection configuration already handle. Test TLS and ACL-restricted credentials in the spike before assuming they work through the UI. If you need enforced least-privilege access, plan to fork the package or use a maintained tool instead.