eve-new-project-setup

Eve New Project Setup

Use this after a developer has run eve init and needs to configure the project for Eve Horizon.

Context

The user has already run:

npm install -g @eve-horizon/cli
eve init my-project
cd my-project

This skill handles the remaining setup: profile, authentication, org/project registration, manifest customization, and git remote configuration.

Step 1: Verify CLI

eve --version

If this fails, the CLI wasn't installed. Have them run:

npm install -g @eve-horizon/cli

Step 2: Profile Setup

Create a profile for the staging environment:

eve profile create staging --api-url https://api.eve.example.com
eve profile use staging

Ask the user for their email and set defaults:

eve profile set --default-email [email protected]

Step 3: Authentication

Check current auth status:

eve auth status

If not authenticated, log in:

eve auth login

The CLI will guide them through SSH key discovery (can fetch from GitHub if needed).

We'll set harness credentials after project creation.

Step 4: Org + Project

Ask the user for:

• Organization name (e.g., "my-company")
• Project name (e.g., "My App")
• Project slug (e.g., "my-app")
• Repo URL (e.g., "[email protected]:me/my-app.git")

Create or ensure they exist:

eve org ensure my-company --slug myco
eve project ensure --name "My App" --slug my-app --repo-url [email protected]:me/my-app.git --branch main

URL impact: The org and project slugs directly form deployment URLs and K8s namespaces:

• URL: {service}.{orgSlug}-{projectSlug}-{env}.{domain} (e.g., api.myco-my-app-staging.eve.example.com)
• Namespace: eve-{orgSlug}-{projectSlug}-{env} (e.g., eve-myco-my-app-staging)
• ${ORG_SLUG} is available for interpolation in manifest values

Slugs are immutable — choose short, meaningful values.

Set as defaults in the profile:

eve profile set --org org_xxx --project proj_xxx