Weave Code
Config Bundle Laravel Package
kunstmaan/config-bundle
A Symfony bundle from the Kunstmaan CMS suite that provides shared configuration utilities and helpers for managing package settings across Kunstmaan applications. It centralizes common config loading and integration points, making it easier to wire CMS features consistently in Symfony projects.
[READ-ONLY] Subtree split of the Kunstmaan ConfigBundle -- master at Kunstmaan/KunstmaanBundlesCMS http://bundles.kunstmaan.be
Frequently asked questions about Config Bundle
- Can I use kunstmaan/config-bundle in a Laravel application?
- No. It is a Symfony bundle built for the KunstmaanCMS suite, and it depends on Symfony's bundle and kernel model plus Doctrine ORM entities. Laravel's service container, Eloquent, and HTTP kernel are different abstractions, so any use in Laravel would be a port rather than an integration. For Laravel, use a native settings package instead.
- What is the Laravel alternative to kunstmaan/config-bundle?
- Use spatie/laravel-settings or a small hand-rolled settings model backed by a cached repository. Both cover the common editable-configuration cases with far less coupling than porting a Symfony CMS bundle. If you need structured config with relations, model it with Eloquent and add a Filament or Nova admin resource.
- Does kunstmaan/config-bundle support Laravel 10 or Laravel 11?
- It has no Laravel version support at all because it is not a Laravel package. Its version constraints track Symfony and KunstmaanCMS releases, not Laravel. Do not add it to a Laravel 10 or 11 composer.json expecting it to work.
- How do I install kunstmaan/config-bundle?
- In a Symfony or KunstmaanCMS project, run composer require kunstmaan/config-bundle, register the bundle in config/bundles.php, and run doctrine:schema:update or generate a migration for the config entity tables. Check the bundle constraint matrix against your Symfony and KunstmaanCMS versions before merging. There is no Laravel installation path.
- What are the requirements for kunstmaan/config-bundle?
- The real constraint is the KunstmaanCMS and Symfony version matrix, plus Doctrine ORM and a compatible PHP version floor. Pin those versions explicitly and resolve conflicts before merging. The PHP version alone is not the deciding factor.
- Is kunstmaan/config-bundle actively maintained?
- It is a read-only subtree split of the KunstmaanBundlesCMS monorepo, so its lifecycle follows that upstream project. Adoption signals are thin, with roughly one GitHub star and zero dependents. The MIT license removes legal risk but not the risk of upstream maintenance slowing or stopping.
- What does kunstmaan/config-bundle actually do?
- It provides shared configuration utilities and custom configuration entities that editors manage inside the KunstmaanCMS admin UI. Application code reads those values back. It centralizes common config loading so CMS features can be wired consistently across Kunstmaan applications.
- How do I migrate config from Kunstmaan ConfigBundle to Laravel?
- Treat it as a conceptual port, not a migration. Define a settings table with key, value, type, and group columns, add an Eloquent model and a cached accessor service, and build an admin resource in Filament or Nova. A modest scope usually takes two to four days. Migrate early because config is read on nearly every request, which makes late migration expensive.
- How should I test editable configuration in Laravel if I drop this bundle?
- Bind a settings repository interface to an in-memory fake in your test suite and assert reads through the cached accessor. Use RefreshDatabase for the underlying settings table and feature tests for the admin resource. Because config is read on nearly every request, also test cache invalidation when a value changes.
- Should I choose kunstmaan/config-bundle or spatie/laravel-settings for a Laravel project?
- For Laravel, choose spatie/laravel-settings. Kunstmaan ConfigBundle is only appropriate inside a KunstmaanCMS or Symfony host where its Doctrine entities and admin UI come for free. On Laravel its architectural fit is effectively zero. The small size of a hand-rolled port is itself evidence that the external dependency buys little.
Weaver
How can I help you explore Laravel packages today?