Deploy and Clean Up One Static App

This walkthrough assumes that the operator authorized your verified OIDC email, first-login provisioning completed after OIDC sign-in, the installer verified the current CLI with its embedded SHA-256, and you completed the explicit-endpoint login. Use disposable content only; this is a non-production DEV environment.

Prepare the directory

Build the site locally. The upload directory must contain only the public files you intend to serve. In this walkthrough it is ./dist.

Do not include credentials, source-only inputs, or private data.

Create one static app

Create the app in the dashboard, or use:

zerokie apps create --name my-site

Keep the generated HTTPS hostname returned for my-site. Custom hostnames are not part of this beta.

Upload the directory directly

zerokie apps deploy my-site --dir ./dist

This is a direct static upload. It does not start a repository build or a container.

Failed overwrites can be visible

Provider-visible static content may be non-atomically changed by a failed overwrite. The operation is not a version promotion and there is no rollback.

If the CLI reports cleanup_failed, stop and contact the operator. Do not continue deploying or try an undocumented recovery.

Open the exact generated HTTPS hostname and verify the expected disposable content.

Revoke and prove rejection

Return to Tokens in the OIDC-authenticated dashboard and revoke the token used for the upload. Then run a read-only CLI request without logging in again:

zerokie apps list

The revoked token must be rejected. Record a failure if the request still authenticates.

Delete the disposable app

Stay signed in through OIDC, open the app in the dashboard, and delete it through that authenticated customer path. Record any cleanup warning and contact the operator; do not use a private workaround.