Deploy your code or any project to Olares — local-run or Market

Source of truth for flags is always olares-cli chart <verb> --help. This file only carries what --help cannot: the three coupled axes of a port, where to start on each, the per-axis concerns to get right, and the gotchas lint won't catch.

Porting baseline: Olares >= 1.12.6. This skill targets Olares >= 1.12.6 (other olares-cli features have no such floor). Check the target with olares-cli profile list (VERSION column). Full version rules — apiVersion: v3, the several chart version fields, type: system dependency — are in references/olares-chart-versioning.md.

Platform model (read once, no login needed for authoring). The porting decisions below rely on the Olares storage model, uid-1000 run identity, app/namespace & networking, system middleware, and version model — all defined once in ../olares-shared/references/olares-platform.md. Packaging an image and authoring/validating the chart need no profile login. Only pushing to a real Olares to test (market upload + install) requires login.

The shape of the work — three axes

Porting an app is not a fixed from-compose → lint → publish pipeline — it is driving three orthogonal but coupled axes each to its own ready state, looping back across the coupling edges as constraints surface (an image's baked-in uid/paths constrain the chart's mounts/permissions; a deploy constraint can send you back to rebuild the image). Start wherever your app already stands, not at a fixed step 1.

• Packaging — the image: the app built into a pullable, arch-correct artifact. Olares only pulls, never builds.
• Deployment — the chart: a lint-passing OlaresManifest + templates. from-compose is only one way in.
• Publishing — the release target: who consumes it — local-run on your own Olares, or market-distribute to the public catalog. This choice gates how strict the other two must be.

First move (not a pipeline): settle the release target (Axis 3) → locate where the app already sits on the packaging and deployment state tables → drive the concerns to ready, looping as constraints surface.

Axis 1 — Packaging (the image)