未通过身份验证 → 继续步骤 4

步骤 4：请求访问权限（仅限新用户）

查找要使用的 SSH 公钥：

ls ~/.ssh/*.pub

默认：~/.ssh/id_ed25519.pub。如果不存在密钥，请生成一个：

ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519

向用户询问：

• 组织名称 — 他们希望如何称呼其组织
• 电子邮件 — 可选，用于其用户账户

提交访问请求并等待批准：

eve auth request-access \
  --ssh-key ~/.ssh/id_ed25519.pub \
  --org "My Company" \
  --email user@example.com \
  --wait

--wait 标志的作用：

1. 提交请求（未认证状态）
2. 打印请求 ID (areq_xxx)
3. 每 5 秒轮询一次，直到管理员批准或拒绝
4. 批准后：自动完成 SSH 质询登录
5. 将令牌存储在 ~/.eve/credentials.json 中

告知用户： "管理员需要运行 eve admin access-requests approve <id> 来批准您的请求。"

一旦获得批准，您将以自己的组织身份（作为管理员）登录。

步骤 5：项目设置

如果已知组织/项目 ID，请设置配置文件默认值：

eve profile set --org <org_id> --project <proj_id>

如果尚不存在项目，请向用户询问：

• 项目名称 和 slug（slug 不可变，请保持简短）

• 仓库 URL（例如：git@github.com:org/repo.git）

  选项 A：确保项目存在

  eve project ensure --name "My App" --slug myapp
  --repo-url git@github.com:org/repo.git --branch main

  选项 B：引导项目 + 环境（单次调用）

  eve project bootstrap --name "My App" --repo-url git@github.com:org/repo.git
  --environments staging,production

URL 影响： Slug 决定了部署 URL：{service}.{orgSlug}-{projectSlug}-{env}.{domain}

步骤 6：清单

如果 .eve/manifest.yaml 不存在，请创建一个最小化的清单：

schema: eve/compose/v2
project: myapp

registry: "eve"

services:
  web:
    build:
      context: .
      dockerfile: Dockerfile
    # image 是可选的；当使用托管注册表时，Eve 会从服务名派生
    ports: [3000]
    x-eve:
      ingress:
        public: true
        port: 3000

environments:
  staging:
    pipeline: deploy

pipelines:
  deploy:
    steps:
      - name: build
        action: { type: build }
      - name: release
        depends_on: [build]
        action: { type: release }
      - name: deploy
        depends_on: [release]
        action: { type: deploy }

使用 eve-manifest-authoring 技能获取详细的清单指导。

步骤 7：了解平台

阅读 Eve 平台参考文档以了解所有功能：

https://web.incept5-evshow-staging.eh1.incept5.dev/llms

内容涵盖 CLI 命令、清单语法、代理工具、作业生命周期等。

步骤 8：验证

eve auth status
eve system health
eve project list

总结

打印已设置的内容：

• 配置文件：名称、API URL
• 身份验证：电子邮件、组织名称、组织 slug
• 项目：名称、slug、仓库 URL
• 后续步骤：同步清单 (eve project sync)、部署 (eve env deploy staging --ref main --repo-dir .)

每周安装次数

148

仓库

incept5/eve-skillpacks

首次出现

2026年2月10日

安全审计

Gen Agent Trust HubWarnSocketFailSnykWarn

安装于

gemini-cli147

codex147

claude-code145

pi54

opencode33

codebuddy33

This calls the API — not a local file check. Two outcomes:

Already authenticated → go to Step 5

If eve auth status shows you're logged in, skip ahead to Step 5: Project Setup.

Not authenticated → continue to Step 4

Step 4: Request Access (New Users Only)

Find an SSH public key to use:

ls ~/.ssh/*.pub

Default: ~/.ssh/id_ed25519.pub. If no key exists, generate one:

ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519

Ask the user for:

• Org name — what they want to call their organisation
• Email — optional, for their user account

Submit the access request and wait for approval:

eve auth request-access \
  --ssh-key ~/.ssh/id_ed25519.pub \
  --org "My Company" \
  --email user@example.com \
  --wait

The --wait flag:

1. Submits the request (unauthenticated)
2. Prints the request ID (areq_xxx)
3. Polls every 5 seconds until an admin approves or rejects
4. On approval: auto-completes SSH challenge login
5. Stores token in ~/.eve/credentials.json

Tell the user: "An admin needs to run eve admin access-requests approve <id> to approve your request."

Once approved, you're logged in with your own org (as admin).

Step 5: Project Setup

Set profile defaults if org/project IDs are known:

eve profile set --org <org_id> --project <proj_id>

If no project exists yet, ask the user for:

• Project name and slug (slug is immutable, keep it short)

• Repo URL (e.g., git@github.com:org/repo.git)

  Option A: Ensure project exists

  eve project ensure --name "My App" --slug myapp
  --repo-url git@github.com:org/repo.git --branch main

  Option B: Bootstrap project + environments in one call

  eve project bootstrap --name "My App" --repo-url git@github.com:org/repo.git
  --environments staging,production

URL impact: Slugs determine deployment URLs: {service}.{orgSlug}-{projectSlug}-{env}.{domain}

Step 6: Manifest

If .eve/manifest.yaml doesn't exist, create a minimal one:

schema: eve/compose/v2
project: myapp

registry: "eve"

services:
  web:
    build:
      context: .
      dockerfile: Dockerfile
    # image is optional; Eve derives it from the service name when managed registry is used
    ports: [3000]
    x-eve:
      ingress:
        public: true
        port: 3000

environments:
  staging:
    pipeline: deploy

pipelines:
  deploy:
    steps:
      - name: build
        action: { type: build }
      - name: release
        depends_on: [build]
        action: { type: release }
      - name: deploy
        depends_on: [release]
        action: { type: deploy }

Use the eve-manifest-authoring skill for detailed manifest guidance.

Step 7: Learn the Platform

Read the Eve platform reference to understand all capabilities:

https://web.incept5-evshow-staging.eh1.incept5.dev/llms

This covers CLI commands, manifest syntax, agent harnesses, job lifecycle, and more.

Step 8: Verify

eve auth status
eve system health
eve project list

Summary

Print what was set up:

• Profile: name, API URL
• Auth: email, org name, org slug
• Project: name, slug, repo URL
• Next steps: sync manifest (eve project sync), deploy (eve env deploy staging --ref main --repo-dir .)

Weekly Installs

148

Repository

incept5/eve-skillpacks

First Seen

Feb 10, 2026

Security Audits

Gen Agent Trust HubWarnSocketFailSnykWarn

Installed on

gemini-cli147

codex147

claude-code145

pi54

opencode33

codebuddy33