EdgeVISS Cloud Manager
Applications & Deployments
Version container-based applications, pull from your own registries, and push a release to one device or an entire fleet — with real deployment status and logs, not a fire-and-forget push.
From registration to a running container
1
Register the application
Name it once — releases are added from its own page as new versions ship.
2
Add a registry provider
Docker Hub, GHCR, Harbor, ACR, ECR, or Google Artifact Registry. Public Docker Hub images need none.
3
Cut a release
A versioned, immutable release tied to one or more container images.
4
Deploy to a device
From the device's own page — pushes down as a signed job on the next poll cycle.
5
Watch it land
Deployment status and streamed logs, per device, right here.
Private registries, no long-lived secrets stored
A registry provider names an environment variable on the Manager process — never a credential stored in the database. Both AWS and Google paths mint a short-lived token fresh on every device poll rather than handing out a durable one.
Docker Hub / GHCR / Harbor / ACR
username:password or token:<PAT> in the named environment variable.
AWS ECR
accessKeyId:secretAccessKey:region — the IAM user needs ecr:GetAuthorizationToken plus pull access.
Google Artifact Registry
Raw service-account JSON, scoped to roles/artifactregistry.reader.
Deployment status is truthful, including recovery
A deployment is pending until it reports back. If a gateway restarts mid-deployment, its outcome is genuinely unproven — that state is surfaced as recovery_required, with the same visual urgency as a confirmed failure, not silently marked successful.