Skip to content

App Operations

Use these commands after an app has been added and deployed.

Inspect

er app list
er app show-details my-app my-server
er app status my-app my-server

er app status reports the app's runtime state on the server:

  • State — running, not running, or not deployed.
  • Readiness — whether the web service is listening on its service.port (listening, not listening, or readiness unknown). A running app can still be not listening if the process hasn't bound its port yet.
  • Containers — each container with its live CPU % and memory use.

Add --json for machine-readable output to script against or pipe into jq:

er app status my-app my-server --json

Server-wide view

er server status <server> shows the same readiness and resource figures for every app on a host at once. See Server Operations.

Logs

er app logs my-app my-server --lines 100
er app logs my-app my-server --since "1 hour ago"

Logs come from the systemd user journal for the containers generated from your service entries.

Lifecycle

er app stop my-app my-server
er app start my-app my-server
er app restart my-app my-server

Redeploy

er app deploy my-app my-server
er app deploy my-app my-server --branch main

Flow A can use --branch. Flow B deploys the stored image references and ignores branch selection.

Remove

er app remove my-app my-server

Data and volumes

Understand where your app stores data before removing or redeploying stateful services. For production databases, prefer managed database providers unless you have a backup and restore plan.