Skip to content
EANVI

Docs

Creating a project

Create projects and environments so secrets stay scoped and versioned.

Creating a project

Projects organize secrets for one application or service. Environments inside a project isolate values for development, staging, production, and previews.

Create a project

  1. Switch to the target organization.
  2. Open Projects → New project.
  3. Set:
    • Name — human-readable label
    • Slug — URL- and CLI-friendly identifier (for example payments-api)
    • Description — optional context for teammates
  4. Save.

Slugs must be unique within the organization. The CLI and SDK address projects by slug.

Create environments

From the project page:

  1. Open Environments.
  2. Add an environment with a slug such as development, staging, or production.
  3. Optionally mark which environment is the default for local work.

Common pattern:

EnvironmentPurpose
developmentLocal machines and feature branches
stagingShared pre-production
productionLive traffic
previewEphemeral preview deploys (CI-created)

Bind the CLI

In your app repository:

eanvi init --project payments-api --environment development

This writes .eanvi/config.json:

{
  "project": "payments-api",
  "environment": "development",
  "envFile": ".env"
}

Commit .eanvi/config.json if the team shares the same project/environment defaults. Never commit credentials or .env.

Rename or delete

  • Update name, description, or settings from the project settings form.
  • Deleting a project removes its environments and secrets — irreversible. Export first if you need a backup.

Next steps