The daily commands

Every command works from anywhere inside a project — dqx walks up to find .dq/config.yml, the way git finds a repository. Standing in a site's directory also picks that site.

Starting and stopping

dqx up	Start every site of the project, and say which one failed rather than reporting success
dqx down	Stop this project
dqx kill	Stop every project on every backend and free 80 and 443; the runtimes keep running
dqx kill --all	That, and the runtimes too, giving their memory back
dqx update	Pull the images this project declares

dqx up also brings up the shared router if it is not running, reissues the certificate when it does not cover a domain yet, and frees a port another project is holding — naming what it stopped.

Working inside a project

dqx shell	A shell in the site, in the directory you are standing in
dqx exec -- <cmd>	One command in the site
dqx composer / npm / artisan / php	The tool, in the right container and directory
dqx test	The project's test suite
dqx run <name>	A command the project declared in commands:
dqx open	The site, in your browser

The database

dqx db	Open the client
dqx db --url	Today's URL, for TablePlus or a dump
dqx db:import <file> / db:export	In and out
dqx snapshot / dqx restore	The database and the storage directories

The published port changes on every up — that is deliberate, so two projects never fight over one port. dqx db --url prints the one that is true now.

Seeing what is going on

dqx info	Every URL, port and connection this project has
dqx info --json	The same, for a script or an agent
dqx list	Every project on the machine, on every backend
dqx logs [service]	Tail logs
dqx doctor	What is broken here, and what to do about it
dqx memory	What each project is costing, and what the VM holds beyond that

Xdebug

dqx xdebug on     # and off, and `dqx xdebug` to see which

Per developer and gitignored, so it never lands in somebody else's checkout, and dqx up re-applies your choice.