Configuration Commands

CLLI provides several commands for managing your configuration file located at ~/.clli/config.json.

config:show

Display the current configuration file contents.

Usage

clli config:show

Output

The command outputs the entire configuration file in JSON format:

{
  "created_at": "2024-01-01 00:00:00",
  "updated_at": "2024-01-01 00:00:00",
  "wp_migrate_license_key": "your-license-key",
  "forge_token": "your-forge-token"
}

Use Cases

• Verify what configuration keys are set
• Check configuration values
• Debug configuration issues

config:update

Interactively update or create configuration values.

Usage

clli config:update

Process

1. The command displays all existing configuration keys (excluding created_at and updated_at)
2. You can select an existing key to update or choose to create a new key
3. Enter the new value for the selected key
4. The configuration is saved automatically

Examples

Update an existing key:

$ clli config:update
Which configuration key would you like to update?
> wp_migrate_license_key
Enter new value for 'wp_migrate_license_key': new-license-key-here
Successfully updated 'wp_migrate_license_key' in configuration.

Create a new key:

$ clli config:update
Which configuration key would you like to update?
> + Create new key
Enter new configuration key: openai_api_key
Enter new value for 'openai_api_key': sk-...
Successfully updated 'openai_api_key' in configuration.

config:delete

Delete a configuration key from the configuration file.

Usage

clli config:delete

Process

1. The command displays all existing configuration keys (excluding created_at and updated_at)
2. Select the key you want to delete
3. The key is removed from the configuration file

Example

$ clli config:delete
Which configuration key would you like to delete?
> openai_api_key
Successfully deleted 'openai_api_key' from configuration.

Notes

• created_at and updated_at are automatically managed and cannot be deleted
• Deleting a key is permanent (but you can recreate it with config:update)

Configuration Keys Reference

Required for Local Development

• wp_migrate_license_key - WP Migrate DB Pro license key
  • Used by: lamapress:new
  • Get from: https://deliciousbrains.com/my-account/licenses

Required for Staging

• forge_token - Laravel Forge API token

  • Used by: lamapress:staging
  • Get from: https://forge.laravel.com/user/profile#/api

• forge_server_id - Forge server ID

  • Used by: lamapress:staging
  • Select from your Forge account servers

• cloudflare_token - Cloudflare API token

  • Used by: lamapress:staging
  • Generate at: https://dash.cloudflare.com/profile/api-tokens

• cloudflare_zone_id - Cloudflare zone ID

  • Used by: lamapress:staging
  • Found in the Overview tab of your domain on Cloudflare

Optional

• openai_api_key - OpenAI API key
  • Used by: ai:story
  • Get from: https://platform.openai.com/api-keys

Manual Configuration

You can also manually edit the configuration file:

# Edit the config file
nano ~/.clli/config.json

Important: Ensure the JSON syntax is valid. Invalid JSON will cause configuration commands to fail.

Related Documentation

• Configuration Guide - Complete configuration documentation
• CLLI Overview - Introduction to CLLI