Weave Code
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

Laravel App Settings Laravel Package

qcod/laravel-app-settings

Add a database-backed settings manager with an admin UI to your Laravel app. Define settings sections/inputs in config, edit them via a Bootstrap 4 page (or custom CSS), and access values via the AppSettings facade. Settings are cached for zero SQL reads.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Build vs Buy: Eliminates 2-3 weeks of custom development for settings UIs by providing a ready-made, cache-optimized solution. Ideal for teams prioritizing speed-to-market over reinventing common infrastructure.
  • Feature Roadmap: Enables non-technical stakeholders to manage app configurations (e.g., branding, email settings, feature toggles) without developer intervention, accelerating iterative product improvements.
  • Use Cases: Critical for applications requiring dynamic runtime configuration (e.g., maintenance mode toggles, user-specific settings via groups), multi-tenant setups, or JavaScript-accessible settings for frontend integrations.
  • Scalability: Database-backed storage with automatic caching ensures zero SQL queries for repeated settings access, supporting high-traffic environments without performance degradation.

When to Consider This Package

Adopt when:

  • You need a quick, secure UI for non-technical users to manage app-wide or user-specific settings.
  • Your project uses Laravel and requires minimal customization (e.g., Bootstrap 4 integration or simple CSS overrides).
  • You need to access settings in JavaScript via global variables or Vue components.
  • Your settings are simple key-value pairs without complex relational data needs.

Look elsewhere when:

  • Your settings require complex data structures (e.g., nested objects, relationships) beyond flat key-value storage.
  • You’re building a pure API without any UI component (use qcod/laravel-settings instead).
  • Your design system requires extensive UI customization beyond the package’s configurable CSS classes.
  • You need centralized configuration across microservices (consider dedicated config services like Consul or AWS AppConfig).

How to Pitch It (Stakeholders)

Executives: "This package delivers a ready-to-use settings management interface in under an hour of integration time, eliminating weeks of custom development. Non-technical teams can instantly update critical configurations—like branding or feature toggles—without developer bottlenecks, accelerating product iterations while reducing operational costs. With built-in caching and security, it scales securely for any user volume."

Engineering: "It’s a battle-tested, cache-optimized solution for database-backed settings with flexible input types (text, selects, images) and zero-config JS integration. Installation is trivial via Composer, and the UI is fully customizable via config. Avoids reinventing a common feature—freeing your team to focus on core product logic while ensuring maintainability and performance."

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.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport