Skip to content
Fullstack Forge

Introduction

create-fullstack-app is a full-stack application scaffold. Run the interactive command line, choose a frontend and backend framework, and it generates an admin panel in the current directory that you can develop, build, and deploy right away.

The generated project is not a hollow shell: login and registration, user management, roles and permissions, dynamic menus, system settings, AI model management, audit logs, full-data import/export, and a dashboard are all built in.

What It Can Generate

Section titled “What It Can Generate”
  • Choice of frontend: React 19 (Vite + TypeScript + Tailwind CSS v4 + shadcn/ui, with PWA) or Vue 3 (Vite + TypeScript + Tailwind CSS v4 + DaisyUI).
  • Choice of backend: Python (FastAPI + SQLAlchemy async + SQLite) or Java (Spring Boot 3.2 + JPA + SQLite/Flyway).
  • Authentication built in: login, registration, logout; Python uses JWT, Java uses Sa-Token; includes login/registration rate limiting and automatic logout on 401.
  • Complete admin panel: users, roles, permissions, menus, system settings, AI models and presets, audit logs, data management, dashboard, and profile.
  • Deployment ready: a single Docker image containing Nginx and the backend, started with one command.

Four Combinations

Section titled “Four Combinations”
Frontend Backend Description
React Python Vite + shadcn/ui, FastAPI async
React Java Vite + shadcn/ui, Spring Boot + JPA
Vue Python Vite + DaisyUI + Pinia, FastAPI async
Vue Java Vite + DaisyUI + Pinia, Spring Boot + JPA

All four combinations implement the same feature set and API conventions, so frontend and backend behave identically and you can choose freely based on your team’s stack. See Stacks and Combinations.

Who It Is For

Section titled “Who It Is For”
  • Teams that need to quickly stand up an admin panel with a permission system.
  • Developers who want to freely combine a React/Vue frontend with a Python/Java backend without reimplementing authentication and permissions.
  • Scenarios that need a complete, readable, modifiable codebase rather than a black-box framework.

Permission Model

Section titled “Permission Model”

API authorization is based on permission points (RBAC) rather than checking role names. Default roles:

  • admin (Administrator): has all permissions.
  • user (Regular user): only view permission for the three menus dashboard, users, and settings.
  • pending_review (Pending review): no permissions.

Newly registered accounts enter either user or pending_review according to the “manual review” switch in system settings. See Permission System.

Dynamic Menus and Data Management

Section titled “Dynamic Menus and Data Management”
  • The sidebar is generated from database-backed groups and items, with global ordering, cross-group dragging, and permission filtering. See Menu Management.
  • Data management provides same-version full export and import. Export uses a one-time random password, import freezes ordinary requests, and a successful restore invalidates every session. See Data Management.

Next Steps

Section titled “Next Steps”