Deploy your code or any project to your Olares

Flags and syntax come from olares-cli chart <verb> --help. Read the shared Olares platform model before porting: chart decisions depend on its storage, uid-1000, namespace, middleware and version semantics.

Authoring (from-compose, lint, package) is local-only. Building for a specific Olares needs the target node architecture before the first image build, and deployment needs the active profile.

Porting targets Olares 1.12.6+; load versioning before writing manifest/chart version and dependency fields.

When to use

• Turn a repo / docker-compose / generic Helm chart into an Olares app, or validate an OlaresManifest; package its image; wire storage / middleware / entrances / env / GPU
• Deploy / run the app on your own Olares (market upload + install); after olares-doctor identifies a chart-owned root cause, edit, lint, and redeploy the chart
• Serve a generation/chat model with an official base app, integrate llm-init, or route an embedding app to the appropriate Market install

This skill owns changes to your chart. olares-doctor finds runtime root causes, olares-market manages published apps, olares-router configures and calls a model once its application is running, and olares-publish prepares a public listing.

The shape of the work — two axes

Porting an app is not a fixed from-compose → lint → deploy pipeline — it is driving two orthogonal but coupled axes each to its own ready state, looping back 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. Once both axes are ready, deploy to the current Olares — an automatic upload + install + diagnose loop.