如何将Laravel配置文件从引用.env改为读取数据库配置？

Got it, let's walk through how to safely replace those .env references with database-driven settings using an Eloquent model in Laravel. I’ll cover the full process, including avoiding common pitfalls like boot order issues and configuration caching.

Step 1: Create the Settings Model & Database Migration #

First, we need a way to store our settings in the database. Let’s generate a model and migration together:

Run this Artisan command to create both files at once:

php artisan make:model Settings -m

Update the Migration File #

Open the generated migration file (found in database/migrations/) and modify the up() method to create a settings table with unique keys and value storage:

public function up()
{
    Schema::create('settings', function (Blueprint $table) {
        $table->id();
        $table->string('key')->unique(); // Ensure each setting has a unique identifier
        $table->text('value')->nullable(); // Flexible storage for different value types
        $table->timestamps();
    });
}

Run the migration to create the table in your database:

php artisan migrate

Update the Settings Model #

Open app/Models/Settings.php and add fillable attributes, plus a helper method to simplify setting retrieval (this saves you from repeating query code everywhere):

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

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

    // Helper method to get a setting with a default fallback
    public static function get(string $key, $default = null)
    {
        $setting = self::where('key', $key)->first();
        return $setting?->value ?? $default;
    }
}

Step 2: Populate Initial Settings #

Next, add your CAPTCHA settings to the database. You can do this via a seeder or manual insertion:

Option 1: Use a Seeder (Recommended) #

Create a seeder file:

php artisan make:seeder SettingsSeeder

Open database/seeders/SettingsSeeder.php and add your CAPTCHA values:

public function run()
{
    \App\Models\Settings::updateOrCreate(
        ['key' => 'CAPTCHA_SECRET'],
        ['value' => 'your-actual-recaptcha-secret']
    );

    \App\Models\Settings::updateOrCreate(
        ['key' => 'CAPTCHA_SITEKEY'],
        ['value' => 'your-actual-recaptcha-sitekey']
    );
}

Run the seeder to insert the data:

php artisan db:seed --class=SettingsSeeder

Option 2: Manual Insert #

If you prefer, run these SQL queries directly in your database:

INSERT INTO settings (key, value) VALUES ('CAPTCHA_SECRET', 'your-actual-recaptcha-secret');
INSERT INTO settings (key, value) VALUES ('CAPTCHA_SITEKEY', 'your-actual-recaptcha-sitekey');

Step 3: Update Configuration via Service Provider (Critical!) #

Important: You can’t directly put Eloquent queries in your config/captcha.php file—Laravel loads configuration files before initializing the database connection, which will throw errors. Instead, use a service provider to dynamically override the config at runtime.

Open app/Providers/AppServiceProvider.php and update the boot() method:

use App\Models\Settings;

public function boot()
{
    try {
        // Fetch settings from database, fall back to defaults if the key doesn't exist
        $captchaSecret = Settings::get('CAPTCHA_SECRET', 'default_secret');
        $captchaSitekey = Settings::get('CAPTCHA_SITEKEY', 'default_sitekey');

        // Override the captcha config values with database data
        config()->set('captcha.secret', $captchaSecret);
        config()->set('captcha.sitekey', $captchaSitekey);
    } catch (\Exception $e) {
        // Fall back to hardcoded defaults if the database is unavailable
        config()->set('captcha.secret', 'default_secret');
        config()->set('captcha.sitekey', 'default_sitekey');
    }
}

Optional: Clean Up the Original Config File #

You can leave your config/captcha.php as-is (it acts as a fallback), or simplify it to:

return [
    'secret' => 'default_secret',
    'sitekey' => 'default_sitekey',
];

Step 4: Handle Configuration Caching #

If you use php artisan config:cache, don’t worry—the service provider’s boot() method runs after the cached config is loaded, so your database-driven settings will override the cached defaults automatically.

When you update a setting in the database, changes will take effect immediately on the next request—no need to clear the config cache.

Testing It Out #

To verify everything works, use config('captcha.secret') in your code—this will now pull the value from your settings table instead of the .env file.

For example, in a controller:

$recaptchaSecret = config('captcha.secret');
// This will return the value stored in your database

内容的提问来源于stack exchange，提问作者Rajasekar D