- Is mrgoodbytes8667/kernel-pack a Laravel package?
- No. Despite being catalogued with Laravel and PHP packages, mrgoodbytes8667/kernel-pack is a Composer metapackage consumed by Symfony Flex, not a Laravel package. It ships no service provider, facade, config-publish tag or extra.laravel.providers entry, so a Laravel application has no integration surface for it. In Laravel, point cache and logs at alternate paths through config/cache.php, config/logging.php and environment variables instead.
- How do I install kernel-pack in a Symfony project?
- It requires Composer 2 with Symfony Flex enabled. Run composer require mrgoodbytes8667/kernel-pack, then inspect the recipe with composer recipes and review the diff before accepting it, because the recipe writes into your project files rather than staying inside a package namespace. Verify the result against a clean checkout in an isolated branch.
- How do I change the cache and log directories in Laravel without this package?
- Set the cache path in config/cache.php and log paths in config/logging.php, or use the CACHE_DRIVER, LOG_CHANNEL and LOG_STACK environment variables. If you need everything under a mounted volume, overriding storage_path or the kernel's cache and log directory methods is usually enough. No third-party pack is needed for this.
- Does kernel-pack support Laravel 10 or Laravel 11?
- There is no declared Laravel support. The package has no Laravel version constraint, no service provider and no Laravel-specific configuration, so it cannot be installed usefully into Laravel 10 or Laravel 11. Treat it as not applicable on a Laravel stack.
- What files does the kernel-pack Flex recipe modify when I install it?
- The recipe mutates existing project files, typically kernel and/or path configuration, instead of confining changes to a package namespace. The exact files depend on the recipe version, so run composer recipes and diff the result before accepting. This is the class of change most likely to conflict silently with existing configuration.
- Is kernel-pack still maintained and compatible with PHP 8.2 or 8.3?
- The last release was 2022-01-05, with zero stars and zero dependents, so compatibility with PHP 8.2, PHP 8.3 and current Symfony recipes is unverified. A recipe can apply cleanly and still produce a broken kernel. Confirm the declared php and symfony/* constraints and test in an isolated branch before scheduling work.
- Can kernel-pack set a custom cache and log path for Docker or a read-only filesystem?
- The need is legitimate for read-only filesystems, shared volumes, ephemeral container storage and multi-tenant isolation. However, you can satisfy it natively by overriding the kernel's getCacheDir and getLogDir methods or by setting container parameters and environment variables. Requiring a stale pack adds a dependency without adding capability.
- What are the alternatives to kernel-pack for alternate cache and log paths?
- For Laravel, use the framework's own configuration: config/cache.php, config/logging.php, storage_path and environment variables. For Symfony, override Kernel::getCacheDir() and Kernel::getLogDir(), or set the relevant container parameters. Both approaches avoid a third-party dependency and stay inside your own codebase.
- How do I review or undo the changes made by the kernel-pack recipe?
- Use composer recipes to list applied recipes, then review the written files with git diff in a dedicated branch. If you want to undo it, revert those files and remove the recipe from your Flex configuration, then reinstall dependencies. Because the recipe edits project files, treat it as an additive and reversible config change only.
- Does kernel-pack work with Symfony 6 or Symfony 7, and which Flex version is required?
- Symfony and Flex version support is unverified. The recipe format and kernel scaffolding may predate current Symfony recipes and PHP 8.2 or 8.3, so check the declared constraints in composer.json. A successful composer require does not prove the generated kernel is compatible.