orama app

orama app

List, get, delete, rollback, and view logs/stats for your deployed applications.

orama app delete <name>

orama app env

Read and change the environment variables a deployed app runs with.

Setting or removing a variable restarts the app, on every node that runs it,
so it picks up the change. The command succeeds only when every node applied
it. If a node could not be reached it is named in the error, still runs the old
environment, and running the same command again retries it.

Values are never printed back. They are where secrets live, so 'list' shows
names only.

orama app env list <app>

orama app env set <app> [flags]

Set one or more variables and restart the app.

Values given with --env never appear in shell history if you read them from a
file instead: --env-file takes a .env and sends every variable in it.

orama app env unset <app> <KEY>...

orama app get <name>

orama app grants

Read and change what a deployment is allowed to reach.

Your app is handed a short-lived token of its own at start, in the file named by
$ORAMA_TOKEN_FILE, and renews it with the gateway before it expires. It reaches
nothing until you grant it something — which is the point: an app that ships
with no credential cannot leak one.

A deployment cannot be granted the control plane. If something needs to deploy
or mint keys, that is a person or a CI key, not an app.

orama app grants list [app]

orama app grants set <app> <role> [flags]

Give a deployment a role in its own namespace.

  runtime  the data plane: invoke, storage, push, webrtc, proxy, pubsub, cache
  reader   nothing beyond the routes that ask for no grant

The change reaches a running app within seconds: a deployment's grant is read
wherever its token is checked (cached for 10 seconds on each node), so it needs
neither a redeploy nor a new token.

orama app list

orama app logs <name> [flags]

orama app rollback <name> [flags]

orama app stats <name>