Weave Code
Setting Module Laravel Package
idavoll/setting-module
A Laravel settings module for centralized, database-backed configuration management. Store and retrieve typed settings, organize values by group, and integrate modular packages through a simple, consistent API.
[READ ONLY] see AsgardCMS/Platform
Frequently asked questions about Setting Module
- What is idavoll/setting-module used for?
- It is a Laravel settings module built specifically for AsgardCMS, providing centralized, database-backed configuration management. You can store and retrieve typed settings, organize values by group, and integrate other Asgard modules through a consistent API. Outside an AsgardCMS host application it is best treated as a reference implementation rather than a drop-in package.
- Can I use idavoll/setting-module in a plain Laravel application?
- Realistically, no. The module assumes AsgardCMS conventions such as the Modules namespace, module manifests, Asgard permission and menu registration APIs, the AdminLTE-based admin theme, and its translation loading scheme. On plain Laravel, Laravel Octane, or a modern Laravel version, the fit is effectively zero because adopting it means adopting AsgardCMS itself. For plain Laravel, evaluate spatie/laravel-settings or a thin custom settings table instead.
- Which Laravel and PHP versions does idavoll/setting-module support?
- Expect AsgardCMS 2.x on Laravel 5.4 through 5.7 and PHP 7.1 to 7.4, in a traditional server-rendered admin setup. It is not viable for Laravel 9+, PHP 8.2+, Livewire or Inertia front ends, multi-tenant SaaS, or API-only services. Always check the composer.json constraints of the exact tag you intend to use, since Composer resolution against a current application will almost certainly conflict.
- How do I install idavoll/setting-module?
- Within an AsgardCMS host, installation is the usual flow: composer require the package, enable the module through the Asgard module manifest, publish config and assets, run the migrations, and seed baseline defaults. Pin the module to an exact tag or commit and vendor it through a Composer path repository or private VCS mirror rather than tracking upstream. Run migrations in staging first and diff the seeded values against what your application currently reads from config files.
- Does idavoll/setting-module store settings in the database or in config files?
- The module is described as database-backed configuration management, so settings are persisted in the database and organized by group. It is worth confirming whether a cache layer exists and whether it is correctly invalidated on save, since stale settings caches are a common source of bugs. Verify this in staging before relying on it in production.
- Is idavoll/setting-module still maintained?
- The technical assessment flags it as effectively dormant: zero stars and zero dependents, with AsgardCMS itself showing little activity for years. Upstream fixes for framework-level security or compatibility issues are unlikely to arrive. If you adopt it, plan to own it as an internal fork and freeze the admin UI as-is rather than expecting updates.
- What license does idavoll/setting-module use?
- The package manifest reports NOASSERTION, meaning the license could not be recognized automatically. Until the actual LICENSE file is read and cleared by legal, commercial use and redistribution remain open questions. In enterprise environments this alone can block adoption, so resolve it before writing any integration code.
- What are good alternatives to idavoll/setting-module?
- For modern Laravel, spatie/laravel-settings is the commonly cited option, or you can build a thin custom settings table with a typed repository and cache layer. If you are already committed to AsgardCMS, this module is the native site-settings subsystem and fits with near-zero friction. If you are not on AsgardCMS, skip this package entirely.
- Does idavoll/setting-module support multi-tenant or per-locale settings?
- That is one of the open questions the technical assessment raises and it is not documented clearly. The description suggests global, single-site grouped settings rather than per-tenant or per-locale scoping. Confirm against the schema and repository code before designing any multi-tenant or localized configuration around it.
- Is there a programmatic API for reading and writing settings outside the admin UI?
- The module exposes a repository-style API for storing and retrieving typed settings by group, which suggests programmatic access is possible. However, the assessment notes that this needs verification because the package may be primarily UI-driven. Wrap all access behind your own SettingsInterface so the underlying implementation can be swapped later without touching call sites.
Weaver
How can I help you explore Laravel packages today?