---
url: /modules/devtools.md
---
# Devtools

Screens for developers inside the panel: the `.env` editor, the application log, the route list, the registered block blueprints and a going-live checklist. Everything here is behind the developer role.

::: glance

* **Module key** `devtools`
* **Default** on
* **Switch** `EVOLVE_MODULE_DEVTOOLS`, see [Modules](/modules/#switching-a-module-on-or-off)
* **Role access** the `developer` role only (`role:developer` middleware), independent of `evolve.roles.modules`, see [Roles](/getting-started/roles#who-is-a-developer)
* **Panel** `/evolve/devtools/`
  :::

## Screens

All under `/evolve/devtools/`, also reachable through Cmd-K ("Variables", "Logs", "Routes", "Block Blueprints", "Going Live Checklist").

| Screen | Path | Does |
|---|---|---|
| Variables | `env` | Reads and edits the `.env` of the environment the panel runs on, every key, with secrets masked. The [Settings](/panel/settings) screen edits a curated subset; this one is the raw file. A save rewrites the file in place without disturbing its structure. |
| Logs | `log` | Reads `storage/logs` through the `logs` disk the module registers. |
| Routes | `routes` | Every registered route with method, URI, name and middleware. |
| Block Blueprints | `block-blueprint` | Every blueprint the install knows, with its fields, grouped by namespace. Useful to see what a module or a published blueprint actually registers. |
| Going Live Checklist | `going-live-checklist` | The checks to run before a site goes live, with their state. |

The panel also offers `phpinfo` at `/evolve/php-info` for developers.

## On a live site

The module is harmless on live as long as the developer role is only given to developers; the `.env` editor shows every secret to whoever has it. Projects that want no developer surface on live set `EVOLVE_MODULE_DEVTOOLS=false` in the live `.env`.