Manage HivePods

Start, stop, restart, suspend and resume

Action	Console	CLI	Notes
Stop	Stop	`hivepod stop web1`	Your files stay. Stopped pods don’t use vCPU or memory from your plan.
Start	Start	`hivepod start web1`
Restart	Restart	`hivepod restart web1`
Suspend	Suspend	`hivepod suspend web1`	Pauses the pod; open terminals are closed.
Resume	Resume	`hivepod resume web1`

The CLI waits until the action finishes; add --no-wait to return straight away.

Startup command

A startup command runs in the background every time the pod starts, for example a web server or a bot. If it exits, it’s restarted after 5 seconds. Its output goes to the pod’s logs. The pod stays up even if the command fails.

Set it when you create the pod (Startup script in the console, --cmd in the CLI), or later with the CLI:

hivepod env web1 --cmd "cd /home/hivepod/projects/app && npm start" --apply

Environment variables

hivepod env web1                         # show current values
hivepod env web1 API_URL=https://... DEBUG=1
hivepod env web1 --unset DEBUG
hivepod apply web1                       # apply pending changes

Changes to variables and the startup command are saved first and take effect when you apply them (hivepod apply, or --apply on hivepod env).

Up to 100 variables; names use letters, digits and _.

Logs and status

hivepod status web1          # status, CPU, memory, uptime
hivepod logs web1 --tail 200
hivepod logs web1 -f         # follow

The console shows resources, current usage and recent output on the pod’s page.

Rename

Rename a pod in its Settings in the console.

Delete

Console: Danger Zone → Delete. There is no going back.
CLI: hivepod rm web1 (add -y to skip the confirmation).

Deleting a pod removes its files, its address and custom domains, and its backups. Restore a backup to a new pod first if you want to keep anything.

Coming soon

Resizing, SSH keys, firewalls, tags and automated backups.