eltavine/pingora-panel

A web operations panel powered by Pingora, with Nginx-like config, Lua scripting, CLI/Web management, and full Docker support.

View on GitHub ↗Jump to charts ↓

eltavine/pingora-panel is written in Rust and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 9th, 2026
Created on August 27th, 2026
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 0
Total Stargazers: 1 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 days
Mean response time: 4.1 days
90th percentile: 7.5 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

Opened in 7 days: 5
Closed in 7 days: 5
Comments in 7 days: 5
Events in 7 days: 10

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Pingora Panel is a self-hosted control plane for managing websites served by a Pingora gateway.

The tool addresses the operational challenge of safely managing gateway configuration across a team. It runs a Pingora-based gateway on a single host and provides centralized management through a web console, CLI, and REST API. Configuration changes flow through a review process: sites, domains, routes, upstreams, listeners, certificates, and policies are edited as drafts, validated, approved according to policy requirements, and applied atomically to the gateway. Every configuration revision is retained and can be compared or rolled back. The draft configuration is stored as Nginx-style files that can be version-controlled, formatted, and diffed. All requests are authenticated and authorized, and a tamper-evident audit trail records every change and rejected attempt.

Teams managing Pingora gateways should consider this tool if they need multi-user configuration management with approval workflows, atomic deployments, and full audit trails. It suits organizations that want to keep gateway configuration in version control while maintaining a centralized control plane. The tool includes traffic monitoring, logging, and alerting alongside configuration management, accessible through the same API that powers the web console and CLI.

The project maintains active build and deployment workflows. Security audits are run regularly. The codebase requires Rust and targets Pingora compatibility.