Skip to content

CLLI Configuration

CLLI stores configuration in ~/.clli/config.json. You'll need to add credentials and license keys for various services to enable full functionality.

Configuration File Location

The configuration file is stored at:

~/.clli/config.json

This file is automatically created when you first use CLLI commands that require configuration.

View Current Configuration

Display your current configuration:

bash
clli config:show

This will output the entire configuration file in JSON format.

Update Configuration

Use the interactive command to update configuration values:

bash
clli config:update

This command will:

  1. Show all existing configuration keys
  2. Allow you to select a key to update or create a new one
  3. Prompt you for the new value

Required Configuration Keys

For full functionality, you should configure these keys:

Local Development

Staging & Deployment

  • forge_token - Laravel Forge API token

  • forge_server_id - Forge server ID

    • Select from your Forge account servers
    • Required for: lamapress:staging
  • cloudflare_token - Cloudflare API token

  • cloudflare_zone_id - Cloudflare zone ID

    • Found in the Overview tab of your domain on Cloudflare
    • Required for: lamapress:staging

Optional

  • openai_api_key - OpenAI API key
    • Required for: ai:story command

Example Configuration

You can manually edit ~/.clli/config.json or use the config:update command:

json
{
  "created_at": "2024-01-01 00:00:00",
  "updated_at": "2024-01-01 00:00:00",
  "wp_migrate_license_key": "your-license-key-here",
  "forge_token": "your-forge-token-here",
  "forge_server_id": "12345",
  "cloudflare_token": "your-cloudflare-token-here",
  "cloudflare_zone_id": "your-zone-id-here",
  "openai_api_key": "your-openai-key-here"
}

Note: The wp_migrate_license_key is the most important for local development. Other keys are primarily used for staging environment management.

Configuration Commands

For detailed information about configuration commands, see the Configuration Commands documentation.

Troubleshooting

Configuration Issues

If configuration is not working:

  1. Check if the config file exists: cat ~/.clli/config.json
  2. Verify JSON syntax is valid
  3. Use clli config:update to interactively update values
  4. Ensure you have write permissions to ~/.clli/ directory

Missing Configuration Keys

If a command fails due to missing configuration:

  1. Run clli config:show to see what's currently configured
  2. Use clli config:update to add the missing key
  3. Refer to the command documentation for required keys

Next Steps

Released under the MIT License.