How kitseno/luna works
Project type and purpose
• This is a full-stack boilerplate combining a Laravel (5.7) REST API backend with a React (16) SPA frontend.
• It offers user management (registration, login, password reset, profile), role/permission enforcement (Laravel-permission & CASL), real-time messaging (Laravel Events/Broadcasting with laravel-echo-server), OAuth2 auth (Passport) and social login (Socialite).
File structure
• Top-level “app”, “config”, “database”, “routes” folders represent the Laravel MVC backend.
• The “resources/js” tree holds the React SPA: entrypoints, components, services, Redux store, routes.
• “public/index.php” serves as PHP front controller; “resources/js/app.js” is Webpack’s React bootstrap.
• Build artifacts are managed by webpack.mix.js and npm scripts; backend uses composer.json.
• There are broadcasting config files for realtime (Echo server), queue workers (jobs in storage, queue:work), notification tables, etc.
README for technical stack
• Backend: Laravel MVC, Passport (OAuth2), Socialite, Events/Listeners, Notifications, Queues.
• Frontend: React, Redux (+ redux-persist), BlueprintJS (UI), Webpack/Mix.
• Real-time: laravel-echo-server + Socket.IO.
• Data store: SQL (migrations), optional Redis (broadcasting, queue).
• External services: social auth providers, mail service.
Detail
• Frontend module grouping (Services, Store, Routes, UI components).
• Integration points (social login, mail, echo server).
• OAuth2 flows (password grant, personal access tokens).