- How do I install islamdb/orchid-setting in a Laravel Orchid project?
- Install it with Composer using composer require islamdb/orchid-setting. Make sure Laravel Orchid is already installed and configured in your application. Then follow the package README for any service provider registration, publishing, or migration steps that are not handled by Laravel auto-discovery.
- Does this package replace Laravel config files?
- No. It stores editable key/value options in the database and gives Orchid administrators ready-made screens and field types for managing them. Keep static application configuration in config files and use this package for values that non-developers need to change from the admin panel.
- Which Laravel and Laravel Orchid versions are supported?
- Check the package composer.json for its exact Laravel and Orchid version constraints before installing. Because it is an Orchid add-on, choose a release that matches the Orchid major version already used by your application. If you are upgrading Orchid, verify compatibility in a staging environment first.
- How are settings organized into groups?
- The package supports grouping key/value options so related settings can be managed together in the Orchid admin panel. Use groups to separate areas such as general site settings, integrations, or feature flags. The exact group creation workflow is handled through the provided screens and field types.
- Can I store typed values such as booleans, numbers, and arrays?
- Yes, the package is designed for typed values and includes field types for editing them from Orchid screens. Use the appropriate field type so values are stored and edited consistently instead of treating everything as a raw string. Confirm the full list of supported field types in the package documentation.
- Do I need to run migrations for the settings table?
- The package stores options in the database, so it needs its settings table to exist before you use the admin screens. Check the README to see whether migrations are loaded automatically or must be published first. After publishing, run php artisan migrate as usual.
- How do I read a stored setting in my Laravel application code?
- Use the accessor or model documented by the package to retrieve settings by key. Avoid querying the underlying table directly so grouping, typing, and any package-level behavior remain consistent. If you need settings in many places, wrap access in your own service or helper.
- Is islamdb/orchid-setting suitable for production use?
- It can be used in production when installed with compatible Laravel and Orchid versions and tested in staging first. Back up the settings table before major changes and review whether your application should cache frequently read options. Also confirm that admin-only screens are protected by your existing Orchid authorization setup.
- How does this compare with spatie/laravel-settings?
- This package is built specifically for Laravel Orchid and provides ready-made admin screens and field types for editing settings. Spatie's package is a more general Laravel settings solution and may require you to build your own admin UI. Choose this package when you want an Orchid-native management experience.
- How can I test setting changes without affecting production?
- Run the package against a testing or staging database and seed the groups and values your tests need. Write feature tests around the admin screens and any application code that reads the settings. Avoid experimenting directly in production, especially when settings control integrations or feature flags.