liberusoftware / project-control-panel-laravel-inertia-react

v0.1.1 2026-11-14 19:32 UTC

Requires

• php: ^8.5
• inertiajs/inertia-laravel: ^3.0
• laravel/framework: ^13.17
• laravel/tinker: ^3.0

Requires (Dev)

• fakerphp/faker: ^1.23
• laravel/pail: ^1.2.5
• laravel/pao: ^1.0.6
• laravel/pint: ^1.27
• mockery/mockery: ^1.6
• nunomaduro/collision: ^8.6
• phpunit/phpunit: ^12.5.12

MIT

• framework
• laravel

Published on Packagist.org on 2026-11-14 20:45 UTC

README

Infrastructure and hosting operations. Laravel routes and sessions with React pages over the Inertia protocol.

This is a presentation skeleton. Product workflows, identity integration and reviewed API adapters must be implemented and verified before production use. Module plans describe intended behavior; they are not installed or published packages.

Based on project-boilerplate-laravel-inertia-react at a227d755c3e70947b06c24ca21a5cb974026b375.

Start locally

Clone this repository, enter its directory and use the declared toolchain and committed lockfiles:

cp .env.example .env
composer install
npm ci
php artisan key:generate
# Configure a new local database, then apply reviewed migrations.
php artisan migrate
npm run build
php artisan serve

Generate an application key only for a new local environment. Keep routes, sessions, CSRF and policy checks on the Laravel side. Select compatible core modules through their actual Composer identities; installation and enablement are separate. Inertia is a page/redirect protocol, not an ordinary REST client. This new shell does not install the full existing Filament module suite or a second identity implementation.

Verify and extend

composer validate --strict
php artisan test
npm run typecheck
npm run build

Read AGENTS.md, integration responsibilities, the presentation runbook and the product scope. Enable one vertical journey at a time against reviewed contracts. Verify allowed, denied, wrong-tenant, expired-session, validation and concurrency outcomes when implementing protected behavior. A pending operation is not a completed business transition.

Other projects using Laravel · Inertia · React

Use the same presentation foundation for other domains. These repositories provide starting structures; their availability does not establish feature parity.

Project	Scope
Boilerplate	Shared application foundation and module composition
Accounting ERP	Ledgers, tax, reporting and finance workflows
Automation	AI gateways, approvals, rules and integrations
Billing	Subscriptions, pricing, payments and provisioning
Browser Game	Game worlds, players and community workflows
CMS	Content authoring, publishing and delivery
CRM	Relationships, sales pipelines and customer service
Ecommerce	Catalogs, checkout, orders and fulfillment
Enterprise SAP	Enterprise workspace and cross-product orchestration
Genealogy	Family trees, research, evidence and collaboration
Liberu Platform	Official sites, staff applications and platform composition
Maintenance	Assets, work orders, schedules and field operations
Music DAW	Composition, recording, sequencing and audio production
Real Estate	Listings, sales, lettings and agency operations
Social Network	Profiles, feeds, communities and moderation

Other presentations for Control Panel

Choose the surface that fits the audience and deployment boundary. The Laravel core remains authoritative across these alternatives.

• Laravel · Filament: PHP/Composer Laravel host with Filament panels.
• Laravel · Inertia · Vue: Laravel routes and sessions with Vue pages over the Inertia protocol.
• Nuxt · Vue: Independent Vue application with Nuxt server rendering and reviewed API integration.
• Next.js · React: Independent React application with explicit Next.js server/client boundaries.
• React Native · Expo: Native iOS/Android application using React Native and Expo.
• Flutter · Mobile: Flutter iOS/Android application using Dart and mobile widgets.
• Dart · Desktop: Dedicated Dart desktop application with a Flutter host for Linux, macOS and Windows.
• Dart · Mobile: Separate Dart mobile application with a Flutter host for iOS and Android.

License and delivery

See the repository license and preserve upstream notices. Review environment configuration, dependencies, backups and rollback before deployment. Publish reusable packages separately from deploying applications. The CI example, where supplied under docs/, must be activated with a credential authorized to manage GitHub workflows.