$ show cedar2025/Xboard
Xboard is a production-grade proxy/VPN subscription management panel built on Laravel 11/12 with Octane (Swoole) for high performance. It manages the full lifecycle of proxy service subscriptions: user registration and authentication, plan selection, order processing with coupon and gift card support, payment integration via a plugin system (Alipay, BTCPay, Coinbase, etc.), and real-time node synchronization through a Workerman WebSocket server. The system generates subscription configurations for multiple client applications (Clash, Surge, Loon, Shadowrocket, SingBox, etc.) using a pluggable protocol abstraction layer. It includes an admin panel with full CRUD for servers, users, orders, tickets, and statistics, plus a Telegram bot plugin for user self-service. The architecture follows Laravel best practices with service classes, form request validation, queue jobs (Horizon), Redis caching, and a custom plugin system that supports both payment gateways and feature extensions. The codebase is well-structured with clean abstractions, though it has a large migration history and some Chinese comments. The project is in limited new feature development mode but actively maintained for critical fixes and security updates.
The LLM identified 4 files worth highlighting for reuse:
Manages the full lifecycle of plugins: install, enable, disable, uninstall, update, and upload. Registers plugin routes, views, providers, commands, and scheduled tasks. Uses a HookManager for action/filter hooks (e.g., order.create.after, traffic.reset.after). Demonstrates a clean, extensible plugin system that can be extracted and reused in other Laravel applications requiring modular feature extensions.
Auto-discovers protocol handler classes in app/Protocols/ by matching a 'flag' property. Provides a unified interface for generating subscription configurations for different client applications (Clash, Surge, Loon, etc.). The pattern allows adding new protocols without modifying core logic, making it reusable for any system that needs to output multiple formats from a common data source.
Tracks user device online status using Redis with TTL and throttled database updates. Normalizes device identifiers (IP, UA) and provides methods to report, check, and count active devices. The pattern of using Redis for real-time state with periodic DB persistence is reusable for any application needing scalable device or session management.
Handles gift card redemption with database transactions and row-level locking (lockForUpdate) to prevent race conditions. Validates card status, applies balance to user accounts, and logs usage. The pattern of using pessimistic locking for financial operations is a reusable approach for any system requiring idempotent and concurrent-safe redemption logic.