hitaqnia / haykal
Haykal metapackage: installs haykal-api + haykal-filament for full-stack projects.
Requires
- php: ^8.3
- hitaqnia/haykal-api: ^3.0
- hitaqnia/haykal-filament: ^3.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
Metapackage for full-stack HiTaqnia Laravel applications.
hitaqnia/haykal is a convenience entry point that installs the two runtime packages in the Haykal suite at once: hitaqnia/haykal-api (API layer, Scramble integration, ApiProvider composition) and hitaqnia/haykal-filament (Filament base classes, shared theme). Both packages transitively install hitaqnia/haykal-core, so a single composer require hitaqnia/haykal brings up the entire stack.
This package contains no PHP code of its own.
When to require this package
Require hitaqnia/haykal when the application exposes both an HTTP API and one or more Filament panels — the typical HiTaqnia project shape.
Applications that only expose an API (headless services, microservices without admin panels) should require hitaqnia/haykal-api directly. Applications that only expose Filament panels (internal admin tools without a public API surface) should require hitaqnia/haykal-filament directly. Both flavors pull haykal-core transitively.
Installation
composer require hitaqnia/haykal
After installation, follow each sub-package's own configuration guide — the metapackage does not add configuration of its own:
haykal-core— remove Laravel's default users migration, wire the auth provider to the application'sUser, publish Spatie permission / Media Library configs, slot middlewares, run migrations.haykal-api— register anApiProviderper module, and for the auth toolkit publishhaykal-auth.phpplus the tokens migration, add thesanctumguard, and mountAuthRoutes::register().haykal-filament— scaffold a panel theme withphp artisan haykal:publish-theme <panel>, define one panel provider per tenant type, and pointloginPage()at the application's own login page.
Requirements
- PHP 8.3 or later
- Laravel 13 or later
- Filament 5.5 or later
Versioning
The metapackage tracks the Haykal suite's major version and pins its dependencies to the matching minor range so composer require hitaqnia/haykal:^3.0 resolves consistent versions of the underlying packages. Pin to a concrete version when you need to lock a release; otherwise composer require hitaqnia/haykal always resolves the latest stable.