Eve Horizon 新项目设置指南：从初始化到部署的完整配置流程

eve-new-project-setup by incept5/eve-skillpacks

162 周安装量

GitHub

安装命令

npx skills add https://github.com/incept5/eve-skillpacks --skill eve-new-project-setup

云服务开发运维命令行工具

🇨🇳中文介绍

Eve 新项目设置

在开发者运行 eve init 后，使用此指南为 Eve Horizon 配置项目。

背景

用户已运行：

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

此技能处理剩余的设置：配置文件、身份验证、组织/项目注册、清单自定义和 git 远程仓库配置。

步骤 1：验证 CLI

eve --version

如果失败，说明 CLI 未安装。请让他们运行：

npm install -g @eve-horizon/cli

步骤 2：配置文件设置

为暂存环境创建配置文件：

eve profile create staging --api-url https://api.eh1.incept5.dev
eve profile use staging

询问用户的电子邮件并设置默认值：

eve profile set --default-email user@example.com

步骤 3：身份验证

检查当前身份验证状态：

🇺🇸English

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.eh1.incept5.dev
eve profile use staging

Ask the user for their email and set defaults:

eve profile set --default-email user@example.com

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 4：组织 + 项目

询问用户以下信息：

组织名称（例如："my-company"）
项目名称（例如："My App"）
项目标识符（例如："my-app"）
仓库 URL（例如："git@github.com:me/my-app.git"）

创建或确保它们存在：

eve org ensure my-company --slug myco
eve project ensure --name "My App" --slug my-app --repo-url git@github.com:me/my-app.git --branch main

URL 影响： 组织和项目标识符直接构成部署 URL 和 K8s 命名空间：

URL: {service}.{orgSlug}-{projectSlug}-{env}.{domain}（例如：api.myco-my-app-staging.eh1.incept5.dev）
命名空间: eve-{orgSlug}-{projectSlug}-{env}（例如：eve-myco-my-app-staging）
${ORG_SLUG} 可用于清单值的插值

标识符是不可变的——请选择简短、有意义的名称。

在配置文件中设置为默认值：

eve profile set --org org_xxx --project proj_xxx

步骤 5：选择 Harness + 设置 API 密钥

询问他们想要定位哪个 harness（可以不止一个）：

mclaude / claude (Anthropic)
code / codex (OpenAI)
zai (Z.ai)
gemini (Google)

将 harness 映射到所需的密钥：

mclaude/claude : ANTHROPIC_API_KEY（首选）或通过 eve auth sync 使用 Claude OAuth
code/codex : OPENAI_API_KEY（首选）或 CODEX_AUTH_JSON_B64
zai : Z_AI_API_KEY
gemini : GEMINI_API_KEY（或 GOOGLE_API_KEY）

决定在哪里存储密钥：

组织（推荐）用于跨项目共享的密钥
项目用于特定应用的密钥
用户用于个人密钥

使用密钥文件进行批量设置（起始仓库包含 secrets.env.example）：

cp secrets.env.example secrets.env
eve secrets import --org org_xxx --file ./secrets.env

对于主机上的 Claude/Codex OAuth 令牌：

# 将 OAuth 令牌存储在项目范围内（如果是管理员，则添加 --system）
eve auth sync --project proj_xxx

步骤 6：清单配置

起始模板包含 .eve/manifest.yaml。使用项目详细信息更新它：

schema: eve/compose/v2
project: my-app

services:
  api:
    build:
      context: apps/api
    ports: [3000]
    x-eve:
      ingress:
        public: true
        port: 3000

environments:
  staging:
    pipeline: deploy

pipelines:
  deploy:
    steps:
      - name: deploy
        action: { type: deploy }

需要自定义的关键字段：

project: 匹配项目标识符
services: 定义你的应用服务
x-eve.ingress: 配置公共访问

步骤 7：Git 远程仓库

项目开始时没有远程仓库。帮助设置一个：

git remote -v
git remote add origin git@github.com:user/my-app.git
git push -u origin main

运行以下检查以确认设置：

eve system health
eve auth status
eve profile show

设置完成后，建议：

本地运行 : docker compose up --build
设置密钥 : eve secrets set MY_KEY "value" 或 eve secrets import --file ./secrets.env
部署到暂存环境 : eve env deploy staging --ref main --repo-dir .
创建任务 : eve job create --prompt "Review the codebase"

注意：如果环境中在清单中配置了 pipeline，eve env deploy <env> --ref <sha> 将触发该流水线。使用 --direct 绕过流水线并直接部署。--ref 必须是 40 个字符的 SHA，或者是相对于 --repo-dir/当前工作目录解析的引用。

"eve: command not found"

npm install -g @eve-horizon/cli

eve profile create staging --api-url https://api.eh1.incept5.dev

Step 3: Authentication

Check current auth status:

If not authenticated, log in:

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

Organization name (e.g., "my-company")
Project name (e.g., "My App")
Project slug (e.g., "my-app")
Repo URL (e.g., "git@github.com: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 git@github.com: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.eh1.incept5.dev)
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

Step 5: Choose Harness + Set API Keys

Ask which harness they want to target (can be more than one):

mclaude / claude (Anthropic)
code / codex (OpenAI)
zai (Z.ai)
gemini (Google)

Map harnesses to required secrets:

mclaude/claude : ANTHROPIC_API_KEY (preferred) or Claude OAuth via eve auth sync
code/codex : OPENAI_API_KEY (preferred) or CODEX_AUTH_JSON_B64
zai : Z_AI_API_KEY
gemini : GEMINI_API_KEY (or GOOGLE_API_KEY)

Decide where to store secrets:

Org (recommended) for shared keys across projects
Project for app-specific keys
User for personal keys

Use a secrets file for batch setup (starter repo includes secrets.env.example):

cp secrets.env.example secrets.env
eve secrets import --org org_xxx --file ./secrets.env

For Claude/Codex OAuth tokens on the host:

# Store OAuth tokens in the project scope (or add --system if admin)
eve auth sync --project proj_xxx

Step 6: Manifest Configuration

The starter template includes .eve/manifest.yaml. Update it with the project details:

schema: eve/compose/v2
project: my-app

services:
  api:
    build:
      context: apps/api
    ports: [3000]
    x-eve:
      ingress:
        public: true
        port: 3000

environments:
  staging:
    pipeline: deploy

pipelines:
  deploy:
    steps:
      - name: deploy
        action: { type: deploy }

Key fields to customize:

project: Match the project slug
services: Define your app's services
x-eve.ingress: Configure public access

The project starts with no remote. Help set one up:

git remote -v
git remote add origin git@github.com:user/my-app.git
git push -u origin main

Step 8: Verification

Run these checks to confirm setup:

eve system health
eve auth status
eve profile show

After setup is complete, suggest:

Run locally : docker compose up --build
Set secrets : eve secrets set MY_KEY "value" or eve secrets import --file ./secrets.env
Deploy to staging : eve env deploy staging --ref main --repo-dir .
Create a job : eve job create --prompt "Review the codebase"

Note: If the environment has a pipeline configured in the manifest, eve env deploy <env> --ref <sha> will trigger that pipeline. Use --direct to bypass the pipeline and do a direct deploy. --ref must be a 40-character SHA, or a ref resolved against --repo-dir/cwd.

"eve: command not found"

npm install -g @eve-horizon/cli

eve profile create staging --api-url https://api.eh1.incept5.dev

Eve Horizon 新项目设置指南：从初始化到部署的完整配置流程

🇨🇳中文介绍

Eve 新项目设置

背景

步骤 1：验证 CLI

步骤 2：配置文件设置

步骤 3：身份验证

🇺🇸English

Eve New Project Setup

Context

Step 1: Verify CLI

Step 2: Profile Setup

相关 Skills

步骤 4：组织 + 项目

步骤 5：选择 Harness + 设置 API 密钥

步骤 6：清单配置

步骤 7：Git 远程仓库

步骤 8：验证

后续步骤

故障排除

"eve: command not found"

"Not authenticated"

"No profile"

Step 3: Authentication

Step 4: Org + Project

Step 5: Choose Harness + Set API Keys

Step 6: Manifest Configuration

Step 7: Git Remote

Step 8: Verification

Next Steps

Troubleshooting

"eve: command not found"

"Not authenticated"

"No profile"

最新 Skills