Skip to content

clie init

Creates a minimal .clie/clie.yml configuration file in the repository root.

This is the first step in setting up CLIE for extension management.

Syntax

clie init [flags]

Description

The init command creates the .clie/clie.yml file in your project.

This file manages extension registration and configuration.

What it does:

  1. Creates the .clie/ directory if needed
  2. Generates a minimal clie.yml with empty extension list
  3. Ready for extension installation via clie install

What it creates:

extensions: []

Flags

Flag Description
--delete-configs Delete all configuration files including overrides
--use-pwd-as-root Use current directory as repository root (creates .git if needed)
-h, --help Display help information

Examples

Basic Initialization

cd /path/to/your/project
clie init

Reset Configuration

Remove all existing configuration and start fresh:

clie init --delete-configs

Three-Step Setup

# Step 1: Initialize CLIE configuration
clie init

# Step 2: Install EAC extension
clie install eac

# Step 3: Configure EAC
clie eac init --ai-provider claude-api

File Structure

After clie init:

your-project/
├── .clie/
│   └── clie.yml      # Extension registry (empty)
└── (your project files)

After clie install eac:

your-project/
├── .clie/
│   └── clie.yml      # Contains eac extension
└── (your project files)

After clie eac init:

your-project/
├── .clie/
│   ├── clie.yml          # Extension registry
│   └── eac/                 # EAC configuration
│       ├── ai-provider.yml
│       └── repository.yml
└── (your project files)

Configuration File

The generated configuration:

# Empty configuration - extensions added via 'clie install'
extensions: []

After installing EAC:

extensions:
  - name: 'eac'
    image: 'ghcr.io/ready-to-release/eac-ext:latest'
    description: 'Everything-as-Code automation'

See Also


Tutorials | How-to Guides | Explanation | Reference

You are here: Reference — information-oriented technical descriptions of the system.