erikdubbelboer/phpRedisAdmin

Simple web interface to manage Redis databases.

View on GitHub ↗Jump to charts ↓Open shareable report →

erikdubbelboer/phpRedisAdmin has 3k+ stars and 650+ forks on GitHub, is written in PHP, and was last pushed on Dec 22, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 21st, 2026
Created on July 6th, 2011
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 664
Total Stargazers: 3,184 (+0)
Total Subscribers: 176 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.5 hours
Mean response time: 16.0 hours
90th percentile: 2.3 days
Tracked items: 13

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 734 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

phpRedisAdmin is a web interface for managing Redis databases.

The tool addresses the need to inspect and manipulate Redis data through a graphical interface rather than command-line tools. It provides a browser-based dashboard where developers can view keys, examine values, and perform administrative operations on Redis instances without requiring direct access to the Redis CLI.

phpRedisAdmin suits developers and operators who prefer visual management of Redis data or need to grant non-technical team members access to database inspection and basic administration. It works well in environments where a lightweight web-based tool is preferable to learning Redis command syntax or where multiple users need controlled access to the same Redis instance. The tool is written in PHP, making it straightforward to deploy on standard web hosting or alongside existing PHP applications.

The project receives infrequent updates with long gaps between commits, suggesting maintenance is minimal and reactive rather than proactive. Pull requests are merged occasionally but not with regularity, indicating the maintainer addresses contributions when they arrive rather than following a structured review schedule. Issue responses are sparse, with many questions and bug reports receiving no reply, reflecting limited active engagement with the user community.