What problem does it solve?
Porting an existing application to the Olares personal cloud requires building arch-correct container images, authoring a valid OlaresManifest, wiring storage, middleware, entrances, environment variables, and GPU resources, then deploying and debugging the result — a multi-axis process with many platform-specific pitfalls that lint alone cannot catch.
Core Features & Use Cases
- Chart authoring and conversion: Scaffold an Olares chart from a docker-compose file with
olares-cli chart from-compose, hand-author an OlaresManifest for a generic Helm chart, validate with chart lint, and package with chart package.
- Image packaging guidance: Build and push pullable, node-architecture-correct images to Docker Hub or ghcr, since Olares only pulls images and never builds from source.
- Deploy and diagnose loop: Upload, install, watch, and iterate on the app against your own Olares cluster, with guidance for runtime failures, permission issues, entrance timeouts, and architecture mismatches.
- Use Case: Take an open-source project that ships only a docker-compose file, convert it into an Olares chart, wire its database as system middleware, build an arm64 image for your node, and deploy it to your own Olares until it reaches the running state.
Quick Start
Ask the AI to port a specific repository or docker-compose file into an Olares app and deploy it to your Olares using olares-cli.