# eve-deploy-debugging

> Deploy and debug Eve-compatible apps via CLI, including local tag workflows, ingress URLs, and failure diagnosis. Use when deployments fail or behavior does not match expectations.

- Author: Adam Chesney
- Repository: Incept5/eve-skillpacks
- Version: 20260122195606
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/Incept5/eve-skillpacks
- Web: https://mule.run/skillshub/@@Incept5/eve-skillpacks~eve-deploy-debugging:20260122195606

---

---
name: eve-deploy-debugging
description: Deploy and debug Eve-compatible apps via CLI, including local tag workflows, ingress URLs, and failure diagnosis. Use when deployments fail or behavior does not match expectations.
---

# Eve Deploy and Debug

Use these steps to deploy and diagnose app issues quickly.

## Deploy flows

- Local k8s loop:
  - `docker build -t ghcr.io/org/app-api:local ./apps/api`
  - `k3d image import ghcr.io/org/app-api:local -c eve-local`
  - `eve env deploy <project> <env> --tag local`
- Registry deploy:
  - Ensure registry secrets exist
  - `eve env deploy <project> <env>`

## Observe deploy

- `eve job list` to find the deploy job.
- `eve job follow <id>` for live logs.
- `eve job diagnose <id>` for errors and timing.
- `eve job dep list <id>` if the job is blocked.

## Common failure points

- Registry auth missing or wrong (`GHCR_USERNAME`, `GHCR_TOKEN`).
- Secrets interpolation missing (`${secret.KEY}` not set).
- Health check failing, blocking readiness.
- Environment gate held by another deploy job.

## Access URLs

- Local ingress: `http://{component}.{project}-{env}.lvh.me`.
- Production: `http://{component}.{project}-{env}.{domain}` (manifest domain or default domain).

## Recursive skill distillation

- Add new deploy pitfalls and fixes to this skill as they appear.
- Extract distinct flows (registry, migrations, health checks) into new skills if needed.
- Update the eve-skillpacks README and ARCHITECTURE listings after changes.