Image Factory State

State and build workflows for container images managed by image-factory.

Images

vibe-kanban

Self-hosted Vibe Kanban remote server — an AI-native kanban board with git worktree-based workspaces.

docker pull ghcr.io/craigedmunds/vibe-kanban:0.1.0
SourceBloopAI/vibe-kanban
Dockerfilecrates/remote/Dockerfile
Registryghcr.io/craigedmunds/vibe-kanban
Port8081
HealthGET /v1/health

backstage

Sourcecraigedmunds/argocd-eda
Registryghcr.io/craigedmunds/backstage

code-server-dev

Sourcecraigedmunds/argocd-eda
Registryghcr.io/craigedmunds/code-server-dev

metrics-service

Sourcecraigedmunds/market-making
Registryghcr.io/craigedmunds/market-making/metrics-service

uv

Sourcecraigedmunds/argocd-eda
Registryghcr.io/craigedmunds/uv

e2e-test-runner

Sourcecraigedmunds/argocd-eda
Registryghcr.io/craigedmunds/e2e-test-runner

Structure

.
├── .github/workflows/    # Build workflows for images without source-repo CI
├── base-images/          # Base image tracking (node, python, distroless, etc.)
├── images/               # Application image state (enrollment, base images, versions)
├── dist/cdk8s/           # Generated Kargo manifests
└── images.yaml           # Enrollment registry — source of truth for all images

How it works

  1. Images are enrolled in images.yaml
  2. task app:generate analyses Dockerfiles, discovers base images, and generates state files
  3. Images without a build workflow in their source repo get one generated in .github/workflows/
  4. image-factory CDK8s app generates Kargo resources for automated rebuilds

0 items under this folder.