- Can I use gnugat/micro-framework-bundle inside a Laravel application?
- No. It is a Symfony bundle that replaces FrameworkBundle with a minimal kernel, event dispatcher, router and DI wiring, so it cannot be loaded inside Laravel's HTTP kernel or a service provider. Running two kernels, two containers and two config systems in one process is a category error, not an integration task. The only workable pattern is out-of-process: a small standalone Symfony service, worker or CLI beside your Laravel monolith, communicating over HTTP, a queue or shared storage.
- Which Laravel versions is gnugat/micro-framework-bundle compatible with?
- Version 0.8.0 requires Symfony 6 and a PHP 8.0 floor, so a Composer co-install spike is now plausible on Laravel 10, which vendors Symfony 6.x transitively. Laravel 11 tracks Symfony 7, and a Symfony 6-only constraint will not resolve there. Check whether the tag declares ^6.0 or ^6.4, since only 6.4 is LTS, and run composer why-not against each Laravel version before assuming anything.
- How do I install gnugat/micro-framework-bundle?
- Install it with Composer in its own project, typically alongside symfony/http-kernel, symfony/routing and symfony/event-dispatcher. Do not add it to an existing Laravel composer.json; keep a separate repository, composer.json, container image and deploy pipeline. Then boot a minimal kernel that registers the bundle instead of FrameworkBundle.
- How do I configure routing and services with this bundle instead of FrameworkBundle?
- You get a curated minimal service set, so you register routes and service definitions yourself through the bundle's configuration and DI wiring. Services that FrameworkBundle normally supplies for free, including validation, serializer, security, profiler and form, are not included and must be hand-wired. That keeps the footprint tiny but pushes real integration work onto you, so budget for it up front.
- Is gnugat/micro-framework-bundle suitable for production?
- It can be, but only for a narrow, well-bounded workload such as a health or metrics endpoint, a small API or a CLI worker. Maintenance is sporadic — 0.8.0 was the first release since February 2022 — with a single maintainer and no dependents. Confirm the bundle is clean on PHP 8.2 or 8.3 before relying on it, and have an exit plan in case the maintainer goes quiet again.
- Is gnugat/micro-framework-bundle still maintained?
- It is marked maintained, and version 0.8.0 ended a gap of more than three years by moving to Symfony 6, PHP 8.0 and PHPUnit 9. A single catch-up release after a long silence is evidence of sporadic maintenance rather than a steady cadence. Ask whether a Symfony 7 release is planned and on what timeline relative to your Laravel 11 upgrade.
- Does gnugat/micro-framework-bundle support Symfony 7?
- Not according to the 0.8.0 constraints, which target Symfony 6 with a PHP 8.0 floor and arrive when Symfony 7 is already current. That is the blocker for Laravel 11, which tracks Symfony 7, so the incompatibility is deferred rather than eliminated. Verify the exact constraint — ^6.4 LTS carries a security runway to roughly late 2027 — before planning around it.
- What are the alternatives to gnugat/micro-framework-bundle for small PHP services?
- Laravel Zero, Slim 4, or a stock symfony/skeleton pinned to Symfony 6.4 LTS usually cover the same use case with better support and documentation. If your team is already on Laravel, Laravel Zero keeps one framework and one skill set instead of adding a second. Pick this bundle only when you specifically want a teeny-tiny Symfony kernel with hand-picked components.
- How do I test a micro-service built with gnugat/micro-framework-bundle?
- Version 0.8.0 moves the test toolchain to PHPUnit 9, so unit and functional tests run under a standard PHPUnit setup in the service's own repository. Do not try to exercise it from inside a Laravel test suite. If the service talks to a Laravel monolith, add contract tests at the process boundary — HTTP, queue or shared storage — rather than mocking across runtimes.
- Should I replace FrameworkBundle with gnugat/micro-framework-bundle in a Laravel-adjacent project?
- No. It is a FrameworkBundle replacement for Symfony applications, and Laravel never consumed FrameworkBundle in that sense, so there is no swap to make. The realistic pattern is additive: one narrow workload deployed separately with its own image, config and composer.json. Do not load its kernel inside an Artisan command or a Laravel service provider, even with the newer Symfony 6 constraint.