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
Description
The init command creates the .clie/clie.yml file in your project.
This file manages extension registration and configuration.
What it does:
- Creates the
.clie/directory if needed - Generates a minimal
clie.ymlwith empty extension list - Ready for extension installation via
clie install
What it creates:
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
Reset Configuration
Remove all existing configuration and start fresh:
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:
After clie install eac:
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:
After installing EAC:
extensions:
- name: 'eac'
image: 'ghcr.io/ready-to-release/eac-ext:latest'
description: 'Everything-as-Code automation'
See Also
- CLIE CLI Overview - Command overview and architecture
- install command - Install extensions after init
- Configuration Reference - Detailed configuration options
- Quick Start Tutorial - Complete setup guide
- CLI vs Extensions - Understanding the architecture
Tutorials | How-to Guides | Explanation | Reference
You are here: Reference — information-oriented technical descriptions of the system.