simplecabinet/simplecabinetwebapi

Purpose and Entry Points

SimpleCabinetWebAPI is a Java backend exposing SimpleCabinet 2 functionality as an HTTP API, including user cabinets, launcher integration, administration, shops, payments, and update delivery. Spring Boot starts from src/main/java/com/gravitlauncher/simplecabinet/web/WebApplication.java; startup initialization is in src/main/java/com/gravitlauncher/simplecabinet/web/WebApplicationOnStartup.java.

HTTP API Boundary

Controllers are grouped by client/domain: public and cabinet APIs, privileged admin APIs, game-launcher APIs, payment-provider webhooks, and an integration endpoint for ban management. DTOs isolate API payloads from persistence models, while centralized exception handling maps domain failures to REST responses.

• src/main/java/com/gravitlauncher/simplecabinet/web/controller/AuthController.java

• src/main/java/com/gravitlauncher/simplecabinet/web/controller/launcher/LauncherAuthController.java

• src/main/java/com/gravitlauncher/simplecabinet/web/controller/admin/AdminMoneyController.java

Authentication and Authorization

Spring Security is configured around JWT issuance, parsing, and request filtering. User/session, permission, group, hardware-ID, and password-check services provide the underlying identity and account controls; controllers operate behind this security boundary.

• src/main/java/com/gravitlauncher/simplecabinet/web/configuration/SecurityConfig.java

• src/main/java/com/gravitlauncher/simplecabinet/web/configuration/jwt/JwtFilter.java

• src/main/java/com/gravitlauncher/simplecabinet/web/service/user/SessionService.java

Core Persistence and Domain Services

The service layer implements business operations over JPA-style model/repository pairs. Persistent domains include users and balances, servers/bans/reputation/news, audit records, shop orders, and launcher-update metadata. Database evolution is managed with Liquibase changelogs.

• src/main/java/com/gravitlauncher/simplecabinet/web/model/user/User.java

• src/main/java/com/gravitlauncher/simplecabinet/web/repository/user/UserRepository.java

• src/main/resources/db/changelog/db.changelog-master.yaml

Registration, Account, and Moderation Flow

Registration and authentication create/manage user records, confirmation/reset preparation, sessions, user assets, and balances. Administrative and cabinet endpoints then manage profile details, security, sessions, hardware, moderation, groups, reputation, bans, and audit history.

• src/main/java/com/gravitlauncher/simplecabinet/web/service/RegisterService.java

• src/main/java/com/gravitlauncher/simplecabinet/web/service/PrepareUserService.java

• src/main/java/com/gravitlauncher/simplecabinet/web/service/AuditService.java

Commerce and Payment Flow

Shop APIs create group, item, or service orders; payment services initiate provider-specific payments and record payment/order state. Webhook controllers receive asynchronous provider callbacks. Delivery is separated by product type, including LuckPerms group fulfillment and database-backed item delivery.

• src/main/java/com/gravitlauncher/simplecabinet/web/service/shop/ShopService.java

• src/main/java/com/gravitlauncher/simplecabinet/web/service/payment/StripePaymentService.java

• src/main/java/com/gravitlauncher/simplecabinet/web/controller/payment/StripeWebhookController.java

Launcher Updates and External Infrastructure

Launcher-facing APIs authenticate clients, expose profiles, check servers, and distribute artifacts/update directories. Artifact storage is abstracted behind local-file or S3 implementations. Configurable integrations include SMTP/console mail, hCaptcha, Stripe, YooKassa, FreeKassa, test payments, and S3; runtime deployment supports a JVM JAR or Docker image.

• src/main/java/com/gravitlauncher/simplecabinet/web/service/updates/LauncherArtifactService.java

• src/main/java/com/gravitlauncher/simplecabinet/web/service/storage/StorageService.java

• Dockerfile