beginner⏱ 3 minutesevnx v0.2.0+

evnx init

Reference documentation for the evnx init command: modes, options, and project setup.

Prerequisites

evnx init — Command Reference

Initialize .env.example and .env files using Blank, Blueprint, or Architect modes with schema-driven variable generation.

Before you start

Bash

evnx init [OPTIONS]

Flag	Type	Default	Description
`--path`, `-p`	`string`	`.`	Output directory for generated files
`--yes`, `-y`	`bool`	`false`	Skip prompts, use defaults (non-interactive)
`--verbose`, `-v`	`bool`	`false`	Enable detailed debug output
`--help`, `-h`	`bool`	`false`	Display help information

Mode	Trigger	Behavior	Best for
Blank	Interactive → Select	Creates minimal `.env` templates	New projects, manual config
Blueprint	Interactive → Select / `--yes` default	Pre-configured stack (e.g., T3, FastAPI)	Quick start with known stacks
Architect	Interactive → Select	Step-by-step: language → framework → services → infra	Custom stack composition

Code	Meaning	Use case
`0`	✅ Initialization completed successfully	Success in scripts/CI
`1`	🚨 Init failed (schema error, write failure)	Fail pipeline on setup issues
`2+`	⚠️ Runtime errors (IO, parsing, validation)	Debug tooling or schema issues

Bash

# Launch mode selector with guided prompts
evnx init

Bash

# Skip prompts, use first available blueprint
evnx init --yes

Bash

# Generate files in ./config directory
evnx init --path ./config --yes

Bash

# Show selection summary and resolution steps
evnx init -v

Bash

# Silent init with custom path for automation
evnx init --yes --path /app/config --verbose

File	Purpose	Overwrite behavior
`.env.example`	Team template with placeholders + docs	Always updated
`.env`	Local secrets (gitignored)	Created only if missing
`.gitignore`	Auto-appends `.env*` patterns	Appends if patterns missing

Variable	Values	Default	Description
`NO_COLOR`	`1`, `true`	`false`	Disable colored output for terminals
`CI`	`1`, `true`	`false`	Auto-enable non-interactive defaults