MiravoPlatforms
Save platform environments, apply and clean up environments, and audit every run — from the browser.
The /platforms page is the Console entry point for provisioning running Miravo environments into supported platforms. Register a target once, apply or clean up from the same page, and audit every run. No CLI credentials required.
Open it from the sidebar, or go to http://127.0.0.1:8080/platforms.
For the CLI equivalents, see CLI ⭢ Platforms. For the quick-start provisioning walkthrough, see Get Started ⭢ Litmus Edge.
Header strip
The header shows, at a glance:
- Number of saved targets
- Total operation count (apply + cleanup runs)
- Outcome of the last operation
Tabs
Three tabs on one page. Mode stays with you across runs.
Environments
The registry of saved platform instances. Each card shows:
- Label
- Platform hostname
- Source host (Miravo) — the address the platform uses to reach your running environment
- A source ⭢ target path indicator
- Outcome of the last operation against this environment
Actions: Add environment, Edit, Remove, Test connectivity.
The API token is never returned to the browser after save. Re-entering the token is the only way to change it — use Edit and set a new token. This matches the behaviour of miravo platforms target update --api-token.
When adding an environment, the platform selector currently shows Litmus Edge as the active option. Other platforms appear as coming soon — selecting them is disabled.
Saved targets are interchangeable with the CLI. Anything saved here is available to miravo apply le --target <label> and miravo cleanup le --target <label>, and vice versa.
Operations
A unified apply and cleanup panel. A mode toggle switches between Apply and Cleanup.
Apply mode:
Pick an environment and a template.
Optional — tick Dry run only and click Preview changes for a plan table. Nothing is written to the platform.
Click Commit deploy to open the confirmation dialog. Configure scopes if needed (devices / models / instances).
Click Apply to execute. A floating stream panel at the bottom of the page shows live progress by phase.
Cleanup mode:
Pick an environment and a template. Optionally tick Remove all Miravo managed resources to ignore template scope.
Click Commit cleanup. Tick Dry run only + Preview changes for a plan table first if you want to confirm the blast radius.
Click Clean up to execute.
Unmanaged resources are never touched
Cleanup operates on resources tagged as Miravo-managed by a prior apply. Pre-existing Litmus Edge content is left alone.
Activity
A persisted audit trail of every apply and cleanup run, stored at ~/.miravo/platforms/operations.jsonl on the server.
- Entries grouped by date
- Expand any row for the run context: scope, filters, duration, outcome counts
- Resource breakdown by phase: DeviceHub tags, DT models, twin instances, parameter sync
- Filter by operation type, status, or environment
- Search by template or environment name
- Load more paginates older entries
Run outcomes you will see: success, partial (some phases failed), failed, dry_run.
Related Console surfaces
The /platforms page is the main provisioning surface, but two others are tied to it.
Tags — Export for Platform
On /tags, the Export for Platform action downloads a platform-ready tag list for the current running environment. For Litmus Edge today: enter the DeviceHub device name, pick which enabled protocols to include, download the CSV. The export matches what miravo export le-tags produces from the CLI.
Catalog — platform exports
On /catalog, each model and template has a platform export available from its inspect sheet.
Model inspect sheet ⭢ Export ⭢ Litmus Edge Digital Twins. Downloads the same JSON that miravo export le-dt --model <name> generates.
Template inspect sheet ⭢ Platform Bridge ⭢ single template JSON ({id}.le-template.json) containing DeviceHub devices, DT models, and instance wiring. Same output as miravo export le-template -t <id>. Ready to import into Litmus Edge ⭢ Template Store ⭢ Import.
Catalog exports do not need a running environment for template export. Model Digital Twins export does require a running environment, because the member list is pulled from the live manifest.
See also
Get Started — Litmus Edge
Quick start, Digital Factory Demo, and one-command provisioning.
CLI — Litmus Edge reference
Every CLI command for Litmus Edge integration.
Console overview
Fleet, Events, Alerts, Tags, Catalog, Control.
Was this page useful?
Last updated on