How v2board/v2board works
Project type and purpose
• V2Board is a monolithic full-stack web application built on Laravel (PHP), serving as a subscription/proxy-management and billing platform. It provides user registration/login, plan management, server provisioning, traffic/statistics, ticketing, payments (Stripe, Alipay, Coinbase, etc.), email/Telegram notifications, and an admin panel.
File structure
• Top-level directories:
• app/ → core Laravel code (Console commands, HTTP controllers by role, Middleware, Jobs, Models, Services, Providers, Plugins, Utilities)
• config/ → environment/configuration
• database/ → migrations, seeds, SQL scripts
• public/ → entry point (index.php), static assets (admin SPA built with Umi/React, theme assets)
• resources/ → Blade views, front-end assets (JS, Sass), i18n, rule templates
• routes/ → route definitions by area (AdminRoute, UserRoute, etc.)
• tests/ → PHPUnit tests
• artisan, bootstrap, storage, composer.json, pm2.yaml, init/update scripts
• Architectural indicators:
• MVC pattern (Controllers, Models, Views)
• Domain services layer (app/Services) and Plugins (Telegram)
• Asynchronous processing (Jobs, Queues, Laravel Horizon)
• Scheduled tasks (Console/Kernel.php)
• Multi-role HTTP entrypoints (Admin, Client, Guest, Staff, Server, Passport, User)
README for additional insights
• Confirms tech stack: PHP7.3+, Laravel, MySQL, Redis
Elements
– Blue for user-facing (frontend)
– Green for application logic (Laravel)
– Yellow for data stores
– Orange for external services