Teploy

Managing Servers

2 min read

There's no server dashboard — teploy is a CLI-first tool, and everything below is a command run against a server over SSH. If you want a web view on top of this, run teploy Dash — a separate, standalone binary that reads the same state.

Status and resource usage

teploy status    # containers, versions, ports for the current app
teploy stats      # live CPU/RAM usage per container
teploy health     # run a health check against the running app

Logs

teploy logs                  # tail container logs
teploy logs --process worker # tail a specific process's logs
teploy logs --lines 200      # show more history
teploy log                   # deploy history: deploys, rollbacks, restarts, failures
teploy log --last 20         # limit entries

Notifications

Deploy/rollback/health-failure events can be pushed out via teploy.yml, not a dashboard setting:

notifications:
  channels:
    - type: slack
      url: https://hooks.slack.com/services/xxx
      events: [deploy, rollback]
    - type: webhook
      url: https://example.com/deploy-webhook

Supported channel types today: webhook (generic JSON POST) and slack (formatted for Slack's Incoming Webhooks). email is accepted in config but not yet implemented. Omit events to receive every event type.

SSH access

Nothing routes through teploy for this — SSH in the normal way:

ssh root@your-server-ip

Or run an ad-hoc remote command through the CLI without a separate SSH session:

teploy exec <server> "docker ps"

Server list

teploy server add <name> <host> --role app --user root
teploy server list
teploy server remove <name>

servers.yml (at ~/.teploy/servers.yml) is the source of truth for connection details — teploy setup writes to it automatically, and these commands manage it directly.

Reboot

Reboot the box the normal way (ssh <host> reboot, or through your VPS provider). teploy's Docker containers are started with restart policies, so app containers, Caddy, and any accessories come back up on their own — nothing needs to be re-run from the CLI afterward.

Removing a server

teploy server remove <name> only removes the entry from servers.yml — it doesn't touch the server itself (doesn't stop containers, doesn't delete data). To actually decommission a server, tear down its containers first (teploy stop, teploy accessory stop) and destroy the VPS through your provider.

On this page