- How do I install nasirkhan/laravel-starter for a new Laravel 13.x project?
- Use Composer’s `create-project` command: `composer create-project nasirkhan/laravel-starter`. Then run `php artisan starter:install` to configure `.env`, database, and assets. Ensure your server meets Laravel 13.x requirements (PHP 8.2+, MySQL/PostgreSQL).
- Can I integrate this starter into an existing Laravel project?
- Yes, but incrementally. Install `nasirkhan/module-manager` separately, then migrate modules one by one using `php artisan module:enable`. Override config files (e.g., `config/module-manager.php`) to match your existing structure. Test thoroughly after each module addition.
- What Laravel versions does nasirkhan/laravel-starter support?
- The package is built for **Laravel 13.x** only. While it may work with minor 13.x updates, avoid mixing with Laravel 12.x or earlier. Pin Laravel to a specific 13.x version in `composer.json` (e.g., `^13.0`) to prevent breaking changes.
- How do I create custom modules for this starter?
- Use the built-in `module-manager` package. Run `php artisan module:make YourModuleName` to scaffold a new module with its own routes, migrations, and assets. Modules auto-register and can be enabled/disabled via `php artisan module:enable/disable`.
- Does nasirkhan/laravel-starter support Docker or Laravel Sail?
- Yes, it works with Laravel Sail. Extend your `Dockerfile` to include custom modules or PHP extensions (e.g., `pdo_pgsql`). Validate Sail compatibility with modules by testing `php artisan sail:publish` and ensuring no conflicts arise during `php artisan starter:install`.
- What if I need to replace the default CoreUI/Bootstrap or Tailwind themes?
- The frontend and backend are decoupled, so you can override themes by publishing assets: `php artisan vendor:publish --tag=coreui-assets` or `--tag=tailwind-assets`. Replace the published files in `resources/assets/` and recompile with `npm run dev` or `npm run prod`.
- How do I handle role/permission updates without cache issues?
- Clear the Spatie permission cache after updates with `php artisan cache:forget spatie.permission.cache`. For bulk changes, use `php artisan permission:cache-reset`. Always test permission logic in a staging environment first to avoid access issues.
- Is nasirkhan/laravel-starter suitable for real-time applications like chat apps?
- No, it’s optimized for content-heavy applications (e.g., CMS, blogs). Livewire introduces reactivity overhead, which may cause latency in high-frequency real-time systems. For chat apps, consider Laravel Echo + Pusher or dedicated WebSocket solutions like BeyondCode’s Laravel WebSockets.
- What are the alternatives to nasirkhan/laravel-starter for modular Laravel apps?
- Consider `orchid/platform` (commercial, monolithic), `filamentphp/filament` (admin-focused), or `spatie/laravel-modular-monolith` (modular but less opinionated). For Livewire-centric starters, check `livewire/livewire` docs or `beyondcode/laravel-breeze-stack`.
- How do I test nasirkhan/laravel-starter in a CI/CD pipeline?
- Use Laravel’s built-in testing tools (`php artisan test`) alongside module-specific tests. Mock Livewire components with `Livewire::test()` and test database transactions in isolation. For Dockerized pipelines, ensure Sail is configured to run tests with `php artisan sail test`.