mcpField
E
eve-project-bootstrap

eve-project-bootstrap

github.com/incept5Cloud & DevOps0294 installsUpdated 17w ago
Repository

About eve-project-bootstrap

A CLI-based workflow for connecting an existing repository to Eve and completing an initial deployment. It guides teams through profiles, organization and project setup, manifest preparation, deployment, and verification.

Key features

  1. 01Configure API profiles
  2. 02Ensure organization and project
  3. 03Prepare Eve manifest
  4. 04Create deployment environments
  5. 05Deploy and verify jobs

Use cases

  1. 01Connect an existing repository to Eve
  2. 02Set up a project and staging environment
  3. 03Trigger a pipeline or deploy directly
  4. 04Check system health and deployment jobs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/incept5/eve-skillpacks --skill eve-project-bootstrap

After installing, type/eve-project-bootstrapin Claude Code to confirm it loaded.

Details

From the project README

Eve Project Bootstrap

Use this flow to connect an existing repo to Eve and get the first deploy running.

Set the API Target

  • Get the staging API URL from your admin.
  • Create and use a profile:
eve profile create staging --api-url https://api.eve.example.com
eve profile use staging

Create Org and Project

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

URL impact: These slugs determine your deployment URLs and K8s namespaces:

  • URL: {service}.{orgSlug}-{projectSlug}-{env}.{domain} (e.g., api.myorg-my-app-staging.eve.example.com)
  • Namespace: eve-{orgSlug}-{projectSlug}-{env} (e.g., eve-myorg-my-app-staging)

Slugs are immutable — choose short, meaningful values.

Set defaults:

eve profile set --org org_xxx --project proj_xxx

Add the Manifest

  • Ensure .eve/manifest.yaml is present and uses schema: eve/compose/v1.
  • Use the eve-manifest-authoring skill for structure details.

First Deploy

# Create environment if needed
eve env create staging --project proj_xxx --type persistent

# Deploy (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .

# If the environment has a pipeline configured, this triggers the pipeline.
# Use --direct to bypass pipeline and deploy directly:
eve env deploy staging --ref main --repo-dir . --direct

Verify

eve system health
eve job list --phase active
eve job follow <job-id>
eve job result <job-id>

Access apps via {service}.{orgSlug}-{projectSlug}-{env}.{domain}.

Comments

Markdown supported