Introduction
laraport is a terminal UI for Laravel apps that run in Docker, on your machine or on servers you reach over SSH. It replaces the chain of ssh, docker ps, docker exec -it … php artisan … with a few keypresses, and it shows what those commands only print: the state of a container, its logs, its queues, its database tables and its files.
What you can do with it
Section titled “What you can do with it”- See every container of every server in one list, grouped by project the way Coolify, Dokploy, Swarm and Compose group them, with live CPU and memory.
con the home screen checks every server at once. - Jump to any container with
ctrl+p, from any screen, even on another server. - Open a container and get a summary of it: health, restarts, ports, the detected stack, and for Laravel apps the versions, environment, drivers and caches from
artisan about. - Read logs of one container or of a whole project, search them, filter by level, jump between errors. Multi-gigabyte log files open instantly, and the errors summary groups a log’s exceptions by kind.
- Find out what happened: which containers died, ran out of memory or restarted, from Docker’s events.
- Work with the Laravel app: run Artisan with autocomplete, run PHP in Tinker, watch queues and Horizon, see the schedule and run a task now, list the routes, check the environment against
.env.example, and run the commands a deploy ends with. - Browse and edit the database the app uses, as a table, with every change shown as SQL before it runs. Restore a dump, browse Redis keys, or open a tunnel for TablePlus or RedisInsight.
- Redeploy, roll back and scale Swarm services, and pull and recreate Compose services.
- Browse, view, edit, upload and download files in a Midnight Commander-style panel.
- Keep the server tidy: images, volumes and networks with their sizes and users, update checks, pruning.
- Stay safe: mark a server read-only, and look back at every change laraport made in the journal.
How it works
Section titled “How it works”laraport runs on your computer. It connects to each server over SSH (or uses the local Docker socket) and runs docker commands there, the same commands you would type. Nothing is installed on the server or in the containers.
Inside a Laravel container it runs small PHP probes in the booted app to read what the app itself knows: its database connections, its queues and Horizon, its schedule. That is why it works with any queue driver or database without needing direct access to them.
Secrets never travel on a command line: passwords and code are passed over stdin. Anything that changes data asks first and shows the exact command or SQL it will run. See Security and privacy.