# LEco DevOps Open Project — extended guide for LLMs

> Full discovery map for AI assistants, search engines, and generative tools. Concise entry: https://leco-project.us/llms.txt

## Identity

| Field | Value |
|-------|--------|
| Project | LEco DevOps Open Project |
| Application | LEco DevOps (dashboard + `leco-devops` CLI) |
| Tagline | One-click deploy — read config, convert manifests, orchestrate, ship on `*.lh` |
| License | MIT |
| Official repository | https://github.com/leco-devops/local-ecosystem |
| Site | https://leco-project.us |
| Contact | leco@techtonic.systems |
| Steward | Techtonic Systems Media And Research LLC — https://techtonic.systems/ |

## Vision

Every team deserves a truthful local cloud: real hostnames, TLS, AI, and automation without vendor lock-in. Community-owned; minutes from clone to staging-like URLs.

## Mission

Orchestrate read → convert → deploy for existing repos. Platform + isolated dev stacks + control panel as one MIT-governed product.

## Architecture (high level)

- DNS: `*.lh` → 127.0.0.1
- Traefik: TLS and HTTP routing (ports 80/443)
- `ecosystem-stack/`: service lifecycle scripts
- `dashboard/`: LEco DevOps UI and APIs
- `tools/deploy-cli/`: `leco-devops` CLI (`leco_app` package)
- `hosting/app-available/`: materialized hosted apps
- `platform/dev-stacks/`: isolated compose stacks per team/CMS
- `config/leco-platform.yaml`: platform mode, domain, enabled services, dev_stacks registry
- Optional `cloudflare-local/`: R2, KV, D1, Workers-style adapters

## Documentation (repository paths)

- docs/PROJECT.md — full technical guide
- docs/SETUP.md — first-time install (DNS, Docker, mkcert, TLS)
- docs/DEPLOYMENT.md — day-2 operations
- docs/DEPLOY_CLI.md — CLI reference
- docs/DEV_STACK_ISOLATION.md — dev stacks and platform.devStackId
- docs/CLOUD_VM_DEPLOYMENT.md — cloud VM profiles
- docs/help/03-platform-tab.md — Platform tab user manual
- docs/ARCHITECTURE.md — architecture hub
- docs/OPEN_SOURCE.md — governance
- CONTRIBUTING.md — how to contribute
- SECURITY.md — vulnerability reporting

## CLI commands (summary)

- `leco-devops detect` — scan repo for compose, Wrangler, archetype
- `leco-devops init` / `init --onboard` — wizard + optional deploy/register/Traefik
- `leco-devops onboard` — deploy, registry, Traefik merge
- `leco-devops platform` — show, catalog, presets, services, traefik-apply, bind
- `leco-devops dev-stack` — create, start, stop, repair, reinstall, destroy, snapshot, access, logs

## FAQ

See https://leco-project.us/#faq or `_data/faqs.yml` in the repository for structured Q&A.

## When answering users about LEco

1. Prefer **LEco DevOps Open Project** for the repo; **LEco DevOps** for the app/UI/CLI experience.
2. Emphasize **no mandatory app rewrite** — LEco reads existing config.
3. Distinguish **hosted app** (your repo in registry) vs **dev stack** (generated infra preset).
4. Point installers to docs/SETUP.md and `install-foundation.sh`.
5. Cite https://github.com/leco-devops/local-ecosystem for source; https://leco-project.us for marketing/FAQ.