Container screen
Summary
Section titled “Summary”▲ laraport › Production › shop-app-1 ● ssh shop.example.com ● shop-app-1 RUNNING ✓ HEALTHY a1 Laravel 13.4.0 · PHP 8.4.14 · production · https://shop.example.com Drivers db pgsql · cache redis · queue redis · session redis · mail smtp · logs daily Cached config ✓ routes ✓ views ✓ events ✓ Packages Horizon 5.33.1 · Filament 4.1.0 · Livewire 3.6.4 Image shop/app:2026.11.3 Uptime up 3mo · since 1 Aug 13:45 · 0 restarts · policy unless-stopped Usage CPU 12.4% · MEM 243M / 2.0G · limit 2 CPU Network :8080->80 · shared 10.0.1.5 · traefik 10.0.2.9 Compose shop / app Command docker-php-entrypoint php-fpm in /var/www/html Mounts /var/www/html/storage Stack Laravel PHP 8.4.14 Node 22.11.0 Composer npm nginx 1.27.2 1 Overview 2 Laravel 3 Logs 4 Docker 5 Files Terminal interactive shell inside the container Info image, status, networks, mounts, labels Stats live CPU, memory, network and disk charts LARAPORT Production shop-app-1 ←→ tabs ↑↓ move enter open 1-5 jump to tab esc back ? help
The top of the screen describes the container and refreshes every 5 seconds while it runs:
- state, healthcheck result and an out-of-memory flag;
- image, uptime and start time, or the exit code and when it stopped;
- restart count and policy;
- live CPU and memory against their limits;
- ports, networks and IP addresses;
- the Compose project and service, or the Swarm stack and service;
- the command, working directory and mounts;
- the stack detected inside, with versions: PHP, Node, nginx, Caddy, FrankenPHP, PostgreSQL, MySQL, MariaDB, Redis, MongoDB.
For a Laravel app it adds what php artisan about reports:
- the Laravel and PHP versions, environment and URL;
- DEBUG ON (red in production) and DOWN (maintenance mode) warnings;
- the database, cache, queue, session, mail and log drivers;
- which caches are built. Uncached config or routes in production are highlighted;
- versions of packages such as Livewire and Filament;
- the migrations, from
migrate:status:✓ all 42 ran, or⚠ 2 pendingwith the first one’s name. See After a deploy.
On short terminals the least important rows go first.
Tabs and actions appear only when the container has what they need. That is checked with one docker exec when the container opens.
| Tab | Actions |
|---|---|
| Overview | Terminal (an interactive shell), Info (docker inspect), Stats (live CPU, memory, network and disk charts with top processes) |
| Laravel | Artisan, Tinker, Queues, Schedule, Routes, Environment, the deploy commands, Composer, npm scripts, your commands, a custom command. Named Run for containers without Laravel |
| Logs | Laravel logs, the errors summary, Docker logs, Service logs |
| Data | Databases, Redis and MongoDB, Redis keys, the app’s own database and Redis, and tunnels to them |
| Docker | Docker commands (inspect, restart, top, diff, ports…), Events, the Swarm service or Compose actions, server cleanup |
| Files | File browser, download storage/ |
← → or tab switch tabs, 1–6 jump to one.
Terminal
Section titled “Terminal”Terminal suspends laraport and attaches your terminal to a shell in the container. Leave it with exit or ctrl+d and laraport comes back where you were. On SSH servers it uses your system ssh -t with the server’s host, port and key.