Metadata-Version: 2.4
Name: dotenv-validator
Version: 1.0.0
Summary: CLI tool to sync and validate .env files against .env.example — detect missing, extra, or mismatched environment variables
License: MIT
Project-URL: Homepage, https://github.com/Major126/dotenv-validator
Project-URL: Repository, https://github.com/Major126/dotenv-validator
Keywords: env,.env,environment,validation,cli,dotenv,sync
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Environment :: Console
Requires-Python: >=3.8
Description-Content-Type: text/markdown

# dotenv-validator

**CLI tool to sync and validate `.env` files** — detect missing, extra, or mismatched environment variables between `.env.example` and `.env`.

## Why?

Every project with environment variables has the same problem:
- You add a new config to `.env.example` but forget to update `.env`
- Someone deploys without the right env vars set
- You waste hours debugging when it's really `DATABASE_URL` missing

## Install

```bash
pip install dotenv-validator
```

## Usage

### Basic comparison
```bash
dotenv-validator
```
Compares `.env.example` with `.env` in current directory.

### Auto-fix missing keys
```bash
dotenv-validator --fix
```

### Strict mode
```bash
dotenv-validator --strict
```

### JSON output (for CI)
```bash
dotenv-validator --json
```

### Initialize .env.example
```bash
dotenv-validator --init
```

### Custom file paths
```bash
dotenv-validator --example .env.dev.example --env .env.production
```

## Use in CI (GitHub Actions)

```yaml
- name: Validate env files
  run: pip install dotenv-validator && dotenv-validator --json
```

## License

MIT
