Skip to content
NewTry Pilot Cloud
Install Pilot

Miren · io.pilot.miren

Miren

Operate the Miren PaaS from an agent: deploy apps, run the server, and debug them. Review setup, usage, and operating details.

Infrastructure · Live on the catalogue

$ pilotctl appstore install io.pilot.miren
Version
v0.1.0
Methods
15
Size
4.8 MB
Permissions
None declared
Platforms
macOS · Linux

About Miren

Miren is a deployment platform for small teams. This app is the app-store front door for the miren CLI, letting an agent drive a Miren PaaS over IPC.

What an agent gets: - Deploy lifecycle — miren.deploy (non-interactive build + deploy), miren.deploy.analyze (detect the stack/services without building), and miren.rollback. - Inspect apps — miren.apps, miren.app (status), miren.app.history, and miren.logs (JSON). - Server & diagnostics — miren.server.install/miren.server.status, miren.doctor, miren.whoami, and miren.debug.connection/miren.debug.advertise. - Full CLI surface — miren.exec runs any verbatim miren argv (addon, auth, env, route, cluster, disk, sandbox, and more).

Good to know: - Structured JSON is returned wherever the CLI offers it (e.g. pass --json). - Discover the live surface at runtime with miren.help — every method, its parameters, and its latency class (fast / med / slow). - Server-side commands need a configured cluster; without one, calls return a structured error ({stdout,stderr,exit}) telling the agent what to do next. - Runs on macOS and Linux (arm64 + amd64); the miren CLI is staged and sha-pinned on install.

Methods · 15

miren.execRun any miren subcommand. Payload is {"args":[...]} — the verbatim miren argv. Use this for the full CLI surface beyond the curated methods below (addon, auth, env, route, cluster, disk, sandbox, etc.). Run `miren help` or `miren --help` for the surface. Example args: ["app","list","--json"]. Note: interactive subcommands (e.g. `app run`, `login`) and long-running ones (e.g. `server start`) are not suitable over IPC.miren.appsList all applications on the cluster (alias for `app list`).miren.appShow the current status of one application. Provide the app name.miren.app.historyShow an application's deployment history.miren.logsRead recent logs for an application as JSON.miren.deployBuild and deploy the app in the current directory (non-interactive, --force).miren.deploy.analyzeAnalyze the app's detected stack/services without building or deploying.miren.rollbackRoll an application back to its previous deployed version.miren.doctorDiagnose the miren environment and connectivity.miren.whoamiShow the current authenticated user and cluster.miren.server.installInstall the miren server as a systemd service on this host (Linux only).miren.server.statusShow miren server service status (Linux only).miren.debug.connectionTest connectivity and authentication with the miren server.miren.debug.advertiseShow which addresses the server would advertise and why.miren.helpDiscovery: every method with params, kind, and latency class.

Full usage demo

When you need to operate a Miren PaaS from an agent — deploy or roll back apps and inspect their status, history, and logs — over IPC.

Run this first — List the applications on your clusterCall
pilotctl appstore call io.pilot.miren miren.apps '{}'
→{"stdout":"[{\"name\":\"web\",\"status\":\"running\"}]","exit":0}

Needs a configured cluster; if none is set up, output is a structured {stdout,stderr,exit} error telling you what to do next.

Worked examples

Show one app's statusCall
pilotctl appstore call io.pilot.miren miren.app '{"name":"web"}'
→{"stdout":"...status...","exit":0}Read recent logs as JSONCall
pilotctl appstore call io.pilot.miren miren.logs '{"app":"web"}'
→{"stdout":"[{\"ts\":...,\"msg\":...}]","exit":0}Build + deploy the app in the current directoryCall
pilotctl appstore call io.pilot.miren miren.deploy '{}'
→{"stdout":"...deployed...","exit":0}

Non-interactive (--force); deploys the CURRENT working directory.

Roll back to the previous versionCall
pilotctl appstore call io.pilot.miren miren.rollback '{}'
→{"stdout":"...rolled back...","exit":0}Reach any miren subcommand (passthrough)Call
pilotctl appstore call io.pilot.miren miren.exec '{"args":["env","list","--app","web","--json"]}'
→{"stdout":"{...}","exit":0}

Good to know

  • Server-side commands need a configured cluster; without one they return a structured {stdout,stderr,exit} error explaining the next step — not a crash.
  • miren.deploy builds and deploys the app in the CURRENT directory non-interactively (--force).
  • Interactive/long-running subcommands (app run, login, server start) aren't usable over IPC — use the curated methods instead.
  • Pass --json inside miren.exec args wherever the subcommand supports it to get structured output.
  • server install / server status are Linux-only.

Next

  • io.pilot.miren miren.help '{}'

What’s New

v0.1.0Latest—
  • Operate the Miren PaaS from an agent: deploy and roll back apps; inspect status, logs, and history; run the server; and diagnose connectivity — plus a passthrough exec for any miren subcommand.

Platform Compatibility

macOSApple Silicon2.9 MBSupportedmacOSIntel2.8 MBSupportedLinuxarm643.0 MBSupportedLinuxamd643.0 MBSupported

More in Infrastructure

All apps