Setting Integration

Some metadata is site-wide rather than per-model: the Facebook App ID, Google verification tokens, the default Open Graph locale and site name. The package reads these from the host application's key/value Setting model when one is available, and falls back to config defaults otherwise — so it never hard-depends on any particular settings implementation.

The settings

Seeding the settings

Run the installer command:

php artisan metadata:install-settings

It is idempotent: existing keys are never overwritten, only missing ones are created. When no usable Setting model exists, it prints a warning and exits successfully without touching anything.

Created setting: METADATA_FACEBOOK_APP_ID
Created setting: METADATA_GOOGLE_SITE_VERIFICATION
...
Installed 8 metadata setting(s).

How the Setting model is detected

The package reads config('oi-laravel-metadata.settings'):

'settings' => [
    'model' => App\Models\Setting::class,
    'key_column' => 'key',
    'value_column' => 'value',
],

A model is "usable" when its class exists and its database table exists. The key_column / value_column make the package work with most key/value schemas without changing your model.

Resolving values in code

The SettingResolver reads a value, falling back to the config default for the key:

use OiLab\OiLaravelMetadata\Support\SettingResolver;

$locale = app(SettingResolver::class)->get('METADATA_OG_LOCALE'); // 'fr' by default

The MetaService and OgService use it internally when rendering, so you rarely call it directly.

Seeding programmatically

The installer is also available as a service:

use OiLab\OiLaravelMetadata\Support\SettingsInstaller;

$installer = app(SettingsInstaller::class);

if ($installer->canInstall()) {
    $created = $installer->install(); // list<string> of created keys
}

This is handy inside your own deploy or seed routines.