Skip to content
Docs

basemodo restart

Restart an App: its Machine starts again on its live Deploy.

Terminal window
basemodo restart [OPTIONS]

It starts with the App's Secrets as they are now, so a Secret set with basemodo env set applies without a new Deploy (waking from sleep does the same). A cron run going on stops. An App paused because a Process kept crashing or ran out of its memory or disk quota is resumed; one paused until its Owner chooses a Plan, or for review, stays paused. Owners and Editors restart an App.

Arguments

  • --app <APP>: The App to restart. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Apply a Secret just set to the App of this folder:

Terminal window
basemodo env set STRIPE_KEY=sk_live_123
basemodo restart

Resume an App paused after its worker kept crashing, once fixed:

Terminal window
basemodo restart --app newsletter

Output

With --json, it prints the App's status after, as status prints it: {"app", "state", "latest_deploy", "public_paths", "extras"}. An App with no live Deploy is an error with code app_not_deployed.

From an agent

The local MCP serves it as the tool restart. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: app (text). It answers what the command prints with --json.

Explained in