Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Settings Bundle

Settings Bundle Laravel Package

swp/settings-bundle

SWP Settings Bundle provides flexible, database-backed application settings for Symfony. Define and organize settings, read and write values at runtime, and manage configuration through a clean service API, with caching to keep lookups fast.

View on GitHub
Deep Wiki
Context7

Scope and owner aware settings system. Define settings in configuration, keep customized values in storage.

Frequently asked questions about Settings Bundle
Is swp/settings-bundle compatible with Laravel?
No. It is a Symfony bundle built around Symfony's dependency-injection container, Doctrine entities and repositories, and SWP's admin UI forms. Laravel cannot consume a Symfony bundle as a Composer package, so adoption would mean porting the domain model, storage, and any UI to Eloquent, Blade, or Livewire. There is no service provider, facade, publishable config, or migrations for Laravel.
How do I install swp/settings-bundle?
It is installed via Composer and registered as a Symfony bundle, not through a Laravel service provider. There is no extra.laravel block, no Laravel config publishing, and no Laravel migrations. On a current Laravel stack, dependency resolution is likely to fail or require heavy version pinning.
Does swp/settings-bundle support Laravel 10 or Laravel 11?
No. The last release was on 2018-06-08, which predates Laravel 6+, PHP 8.x, Symfony 5+, and Doctrine DBAL 3. There is no compatibility guarantee, and the Symfony bundle lifecycle has no Laravel equivalent. Expect to need a full static-analysis pass and dependency audit before any attempt.
What is swp/settings-bundle used for?
It provides key-value application settings with a getter and setter service API, dependency-injection integration, and caching for fast lookups. It is intended for Symfony applications that need admin-editable preferences and feature flags. It is not designed or maintained as a Laravel settings package.
How is swp/settings-bundle configured in Laravel?
It is not configured in Laravel at all. Configuration happens through Symfony bundle registration and dependency-injection wiring, not Laravel config files. To use the same domain in Laravel, you would reimplement the settings model and storage on Eloquent with a repository or cache decorator.
Is swp/settings-bundle still maintained?
No active maintenance is evident. The repository is a read-only subtree split of the Superdesk Web Publisher monorepo, and pull requests to this repo are rejected by design. Fixes must flow through the upstream monorepo, which is itself dormant, so there is no clear path for security patches.
What license does swp/settings-bundle use?
It inherits AGPL-3.0 from Superdesk Web Publisher. That viral copyleft is a likely disqualifier for proprietary SaaS or commercial on-prem products. Have legal review network-use, distribution, and source-disclosure obligations before vendoring any code.
Can I use swp/settings-bundle with PHP 8?
Not safely. The 2018 release predates PHP 8.x and likely contains PHP 7.1 to 7.3 syntax plus Symfony 3 or 4 and Doctrine DBAL 2.x assumptions. Any adoption requires a full static-analysis pass and dependency audit, and resolution may still fail on current PHP versions.
What are the best Laravel alternatives to swp/settings-bundle?
For Laravel, spatie/laravel-settings is the conventional choice for typed, cached settings. A simple settings table with an Eloquent model and a cache decorator also covers global, tenant, and user scopes. Plain config remains appropriate for values that do not need runtime editing.
Is swp/settings-bundle production-ready for a new Laravel project?
No. It has 1 star, 0 dependents, no issue triage, stub-level documentation, and no third-party evidence that it works outside SWP's own application. The technical risk is high across abandonment, compatibility, licensing, and maintenance, with no upstream support path. For a new Laravel project, use a maintained Laravel package or build a small native settings layer.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo