Laravel Debug FAQs

Question 1

What is Laravel Debug?

Accepted Answer

Laravel Debug is a production-safe tool that enables secure debugging and diagnostic operations for Laravel applications. It integrates with Codex CLI and uses an SSH-based runner to access production hosts without granting full shell access.

Question 2

What types of diagnostic information can I gather with Laravel Debug?

Accepted Answer

You can gather comprehensive information including Laravel health checks, Artisan command output (version, about, migrations, schedule, queue failed), application logs (list, tail, grep, last error), system metrics (disk, memory, top), PHP version, and Laravel cache artifacts status.

Question 3

How does Laravel Debug ensure production safety?

Accepted Answer

It ensures safety through a secure SSH connection to a remote runner that executes only a strict allowlist of curated, read-only commands. This architecture avoids public exposure and uses a dedicated, locked-down SSH user with forced commands for enhanced security.

Question 4

What are the core requirements to use Laravel Debug?

Accepted Answer

Locally, you need Node.js (>=18), Codex CLI, and SSH access to your production host. On the remote server, PHP CLI, common utilities like `tail` and `grep`, and a dedicated, restricted SSH user are required.

Question 5

Does Laravel Debug allow any write or mutation operations?

Accepted Answer

By default, Laravel Debug is read-only. However, it offers optional 'break-glass' mutation operations, such as restarting queues (`artisan queue:restart`). These are double-gated, requiring explicit local and remote environment variables to be enabled, ensuring maximum control and security.

Laravel Debug

Laravel Debug

主な機能

ユースケース

主な機能

ユースケース