Loading...
update - Update ComponentsUpdate Apito engine, console, or the CLI itself.
Usage:
apito update <engine|console|self> [-v <version>]
Examples:
# Update engine to latest version
apito update engine
# Update console to a specific version
apito update console -v v1.2.3
# Update the CLI itself to the latest version
apito update self
The CLI automatically manages engine and console versions with smart update detection:
During apito init (Docker mode):
~/.apito/config.ymldocker-compose.yml with specific version tagsDuring apito start (Docker mode):
docker-compose.yml with updated versionsVersions are stored in ~/.apito/config.yml:
mode: docker
engine_version: v1.3.1
console_version: v2.5.0
# Start will check for updates
$ apito start
# If updates are available, you'll see:
🆕 Updates Available
Engine: v1.3.0 → v1.3.1
Console: v2.4.0 → v2.5.0
? Choose update action:
▸ Update Engine (v1.3.0 → v1.3.1)
Update Console (v2.4.0 → v2.5.0)
Update Both
Skip Updates
# After selecting, the CLI will:
✓ Pulling Docker image: ghcr.io/apito-io/engine:v1.3.1
✓ Successfully pulled ghcr.io/apito-io/engine:v1.3.1
✓ Updated engine to v1.3.1
✓ docker-compose.yml updated
config.yml to downgrade if neededYou can manually set versions in config.yml:
engine_version: v1.2.0 # Downgrade to specific version
console_version: latest # Use latest tag
Then regenerate docker-compose.yml:
apito init # Will respect your manual version settings