創(chuàng)建一個(gè)數(shù)據(jù)庫(kù)表和模型用於存儲(chǔ)鍵值對(duì)設(shè)置；2. 創(chuàng)建一個(gè)服務(wù)類(lèi)（SettingService）來(lái)封裝獲取、設(shè)置和刪除設(shè)置的邏輯，並實(shí)現(xiàn)內(nèi)存緩存；3. 在服務(wù)提供者中將服務(wù)註冊(cè)為單例以便依賴(lài)注入；4. 可選地創(chuàng)建門(mén)面（Facade）以支持全局靜態(tài)調(diào)用如Setting::get()；5. 可選地創(chuàng)建控制器和管理界面用於通過(guò)表單更新設(shè)置；6. 在應(yīng)用啟動(dòng)時(shí)預(yù)加載常用設(shè)置到配置中以提升性能；該系統(tǒng)通過(guò)數(shù)據(jù)庫(kù)動(dòng)態(tài)管理應(yīng)用級(jí)配置，適用於可由管理員修改的設(shè)置項(xiàng)，不替代.env中的環(huán)境變量，具有良好的擴(kuò)展性和復(fù)用性，完整實(shí)現(xiàn)了一個(gè)靈活的Laravel設(shè)置管理系統(tǒng)。

Creating a settings management system in Laravel allows you to store, retrieve, and update application-level configuration values dynamically—like site name, contact email, theme options, or API keys—without hardcoding them or relying solely on .env files.

Here's how to build a flexible and reusable settings system in Laravel.

1. Create a Settings Database Table and Model

First, create a database table to store key-value pairs for your settings.

Run the migration:

 php artisan make:migration create_settings_table

In the migration file:

 Schema::create('settings', function (Blueprint $table) {
    $table->id();
    $table->string('key')->unique();
    $table->text('value')->nullable();
    $table->timestamps();
});

Run the migration:

 php artisan migrate

Now create a model:

 php artisan make:model Setting

Optional: Add mass-assignable fields in the Setting model:

 class Setting extends Model
{
    protected $fillable = ['key', 'value'];
}

2. Create a Settings Service or Facade

To make accessing settings easy throughout your app, create a service class.

 php artisan make:service SettingService

If make:service isn't available, just create app/Services/SettingService.php manually.

 namespace App\Services;

use App\Models\Setting;

class SettingService
{
    protected array $cache = [];

    public function get(string $key, mixed $default = null): mixed
    {
        if (! array_key_exists($key, $this->cache)) {
            $setting = Setting::where('key', $key)->first();
            $this->cache[$key] = $setting?->value ?? $default;
        }

        return $this->cache[$key];
    }

    public function set(string $key, mixed $value): void
    {
        Setting::updateOrCreate(['key' => $key], ['value' => $value]);
        $this->cache[$key] = $value;
    }

    public function forget(string $key): void
    {
        Setting::where('key', $key)->delete();
        unset($this->cache[$key]);
    }

    public function all(): array
    {
        return Setting::pluck('value', 'key')->toArray();
    }
}

3. Bind the Service in Service Provider (Optional)

To make the service easily injectable, bind it in AppServiceProvider or create a SettingServiceProvider .

In app/Providers/AppServiceProvider.php :

 use App\Services\SettingService;
use Illuminate\Support\ServiceProvider;

public function register()
{
    $this->app->singleton(SettingService::class, function ($app) {
        return new SettingService();
    });
}

Now you can inject SettingService into controllers, middleware, or views.

4. Create a Facade (Optional but Convenient)

Create a facade for easier access like Setting::get('site_name') .

First, create app/Facades/Setting.php :

 namespace App\Facades;

use Illuminate\Support\Facades\Facade;

class Setting extends Facade
{
    protected static function getFacadeAccessor()
    {
        return \App\Services\SettingService::class;
    }
}

Register it in config/app.php under aliases:

 'Setting' => App\Facades\Setting::class,

Now you can use:

 use Setting;

$value = Setting::get('site_name');
Setting::set('contact_email', 'admin@example.com');

5. Create an Artisan Command to Clear Settings Cache (Optional)

Since we're caching in memory during a request, no persistent cache is used here. But if you later add Redis or config caching, you might need a command to clear.

For now, it's not needed unless you expand the system.

6. Add a Controller and Admin Interface (Optional)

To manage settings via UI:

 php artisan make:controller Admin/SettingController

Example method to list and update settings:

 use App\Services\SettingService;
use Illuminate\Http\Request;

public function index(SettingService $service)
{
    return view('admin.settings', ['settings' => $service->all()]);
}

public function update(Request $request, SettingService $service)
{
    foreach ($request->except('_token') as $key => $value) {
        $service->set($key, $value);
    }

    return back()->with('success', 'Settings saved.');
}

Blade example ( resources/views/admin/settings.blade.php ):

 <form method="POST">
    @csrf
    <input name="site_name" value="{{ Setting::get(&#39;site_name&#39;) }}">
    <input name="contact_email" value="{{ Setting::get(&#39;contact_email&#39;) }}">
    <button type="submit">Save</button>
</form>

7. Load Settings on Boot (Optional Performance Optimization)

If you always use certain settings, preload them when the app boots.

In a service provider (eg, AppServiceProvider@boot ):

 public function boot(SettingService $service)
{
    // Preload common settings if needed
    config([
        'mail.from.address' => $service->get('contact_email'),
        'app.name' => $service->get('site_name'),
    ]);
}

Or use middleware to preload all settings once per request if needed.

Final Notes

• This system is dynamic and database-driven.
• It's ideal for admin-modifiable settings.
• For performance, consider caching with Laravel's cache system (eg, Redis) if you have many settings.
• Don't replace .env for environment-specific config (like DB credentials)—use this for user-editable application settings.

Basically, just create a model, wrap it in a service, and optionally add a facade and UI. It's simple, reusable, and scales well.

以上是如何在Laravel創(chuàng)建設(shè)置管理系統(tǒng)？的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！