- Is BaksDev Core compatible with Laravel 10, or should I use it only for Symfony projects?
- BaksDev Core is a Symfony bundle, not natively Laravel-compatible. While it can work in hybrid projects (e.g., Lumen + Laravel), Laravel 10’s PHP 8.2–8.3 support conflicts with its PHP 8.4+ requirement. For pure Laravel, consider Spatie or Laravel’s built-in tools instead.
- How do I configure the `HOST` domain in Laravel’s `.env` for BaksDev Core?
- Add `HOST=yourdomain.example` to your Laravel `.env` file. This is required for systemd worker naming conventions and domain-aware routing. Ensure the domain matches your project’s primary URL to avoid conflicts with multi-tenant setups.
- Can I replace Laravel’s Task Scheduling with Symfony Scheduler from BaksDev Core?
- No, not directly. Symfony Scheduler and Laravel’s `schedule:run` are incompatible. If you need Symfony’s Scheduler, isolate it to a Lumen microservice or use a facade to abstract calls, but expect maintenance overhead for dual stacks.
- Will BaksDev Core’s systemd workers work in Docker or Kubernetes instead of Linux systemd?
- No, the package assumes systemd. For Docker/Kubernetes, replace systemd workers with Supervisor or CronJob alternatives. The package provides no built-in support for containerized environments, requiring custom scripts or infrastructure changes.
- Does BaksDev Core interfere with Laravel Mix or Vite for asset compilation?
- Yes, its `baks:assets:install` script uses Symfony CLI tools, which may conflict with Laravel Mix/Vite. If you rely on WebP conversion via Files Cdn, you’ll need to integrate it separately or disable the conflicting scripts in `composer.json`.
- How do I integrate Symfony Messenger into Laravel without breaking Horizon?
- Use a facade to abstract Messenger calls or deploy it as a separate Lumen microservice. Direct integration risks conflicts with Laravel’s queue system. For production, test thoroughly—Symfony Messenger’s systemd workers won’t work with Laravel’s Horizon by default.
- Are there Laravel alternatives to BaksDev Core’s asset automation and CLI scripts?
- Yes. For assets, use Laravel Mix/Vite or Laravel’s `mix` facade. For CLI automation, extend Artisan with custom commands. Packages like Spatie’s `laravel-activitylog` or `laravel-backup` offer Laravel-native alternatives to BaksDev’s scripts.
- How do I test BaksDev Core in a Laravel project if its tests are Symfony-specific?
- Run `php bin/phpunit --group=core` as documented, but expect failures due to Laravel-Symfony mismatches. Mock Symfony dependencies (e.g., Messenger) in Laravel’s testing environment or adapt tests to use Laravel’s equivalents (e.g., Queues instead of Messenger).
- Can I use BaksDev Core’s translation system in Laravel instead of Laravel’s built-in `trans()`?
- Technically yes, but it’s unnecessary. Replace Symfony’s Translation component with Laravel’s `trans()` via a service provider. The bundle’s translation features add dependency bloat without Laravel-specific benefits.
- What’s the long-term viability of BaksDev Core for Laravel projects given its Symfony focus?
- Low to medium. The package is new (likely 2026 placeholder), lacks English docs, and has no community adoption. If you’re committed to a hybrid Symfony/Laravel stack, proceed cautiously. For pure Laravel, prioritize native packages like Spatie or Laravel’s core features.