Processes and isolation
Separate frontend processes, workers, and data for each project.
Start the whole project
In Project Processes, select frontend, queue worker, scheduler, and broadcasting. Start Project applies that selection. Stop stops its processes while leaving nginx, PHP, and shared services running.
yard project:configure my-project --frontend --queue --scheduler --no-broadcasting
yard project:start my-project
yard project:processes my-project
yard project:stop my-project
Laravel workers require artisan; broadcasting requires Reverb in the project.
Isolate project data
Isolate this project separates the database, cache, queue, session cookies, and mailbox if the project already uses Yard SMTP. It is not operating-system security isolation.
SQLite is copied with its backup API. MySQL, MariaDB, and PostgreSQL receive a new empty database: run migrations. Disabling isolation restores previous connections and preserves isolated data.
yard project:isolate my-project
yard project:unisolate my-project
Diagnostics and audits
Check inspects the directory, runtimes, and dependencies. Run Audit checks pinned dependencies against security advisories without updating them; registry access is required. Review logs, sample data, and attached screenshots before sharing reports. See the environment reference.