> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enver-os.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# ev init

> Initialise an Enver project in the current directory.

# ev init

Creates a `.ev.json` configuration file in the current working directory, linking it to an Enver project.

## Usage

```bash theme={null}
ev init
```

## Interactive prompts

| Prompt              | Description                                                      |
| ------------------- | ---------------------------------------------------------------- |
| Project ID          | A unique slug (alphanumeric and hyphens). Used in all API calls. |
| Project name        | A human-readable display name.                                   |
| Default environment | `DEVELOPMENT`, `STAGING`, or `PRODUCTION`.                       |

## Output file: `.ev.json`

```json theme={null}
{
  "projectId": "my-saas-app",
  "name": "My SaaS App",
  "defaultEnvironment": "DEVELOPMENT"
}
```

## Example

```bash theme={null}
cd ~/projects/my-saas-app
ev init
```

```
? Project ID: my-saas-app
? Project name: My SaaS App
? Default environment: DEVELOPMENT
✓ Created .ev.json in current directory
```

<Tip>
  Commit `.ev.json` to your repository so teammates don't have to run `ev init`. Add `.env` and `~/.enver/config.json` to `.gitignore`.
</Tip>
