Logs & Terminal
Stream live logs and open a shell inside any running container.
When something's not right, you need to see what your app is actually doing. Better-PaaS gives you two tools: live logs and an in-browser terminal.
Live logs
Open an app and go to the Logs tab to see its output (stdout and stderr) streaming in real time over a WebSocket — exactly what your app is printing, as it prints it.
Logs survive restarts
Container output is also persisted to disk, so you don't lose history when a container restarts or redeploys. You can scroll back through past output, not just whatever happened since the last restart.
Logs are your first debugging stop
Most problems — a crash on startup, a failing request, a misconfigured env var — show up clearly in the logs. Check here before digging deeper.
In-browser terminal
The Terminal tab opens an interactive shell inside the running container. It's like SSHing into just that app, straight from your browser.
Need a shell on the host instead?
The container terminal is scoped to a single app. To get a shell on the host machine running Better-PaaS, use the Server Terminal in the sidebar.
Use it to:
- Inspect files and check the environment (
env,ls,cat) - Run one-off commands or scripts
- Manually test a database connection
- Debug why something isn't behaving
# See what environment variables the app received
env | sort
# Check the app is listening on the expected port
netstat -tlnp 2>/dev/null || ss -tlnpChanges in the terminal aren't permanent
The container filesystem resets on the next redeploy (except for volumes). Use the terminal for inspection and debugging — make lasting changes in your code or config and redeploy.
Host-level metrics
Beyond per-app logs, the Health screen shows overall server CPU, memory, and
disk usage, and each app's Overview tab shows that app's live CPU/memory from
docker stats.