Configuration

In the ignition config file you can tweak the way the Ignition error page behaves and looks like.

Setting your editor

On a typical error screen paths to source file names are displayed. Next to the file name is a pencil icon. Clicking the pencil icon will open that file in your editor of choice. You can configure that editor in the editor key of the ignition config file.

You can choose between phpstorm, vscode, vscode-insiders, sublime, and atom.

Theme support

You can configure a theme in the theme key of the ignition config file. Out of the box there are two beautiful themes supported.

light

Screenshot of light ignition theme

dark

Screenshot of dark ignition theme

You can also specify auto. Ignition will then follow the preference set for your OS.

Remote Development Server Support

To allow the edit URL to be created properly, you should specify the following variables in your .env file. Leave these empty if you are developing locally and are serving your site from the same filesystem you are editing on.

In the remote_sites_path config key, you can specify the full path (not URL) to your projects or sites folder on your remote dev server, be this Homestead, Docker, or in the cloud .

In the local_sites_path config key, you can specify the full path (not URL) to your projects or sites folder as it resides on your local machine, the way your IDE or editor accesses the files.

Ignoring exceptions & error

Ignition will always send all exceptions Laravel reported to Flare, when a Flare application is configured. You can change this behaviour by filtering the exceptions with a callable:

Flare::filterExceptionsUsing(
    fn(Throwable $throwable) =>  !$throwable instanceof AuthorizationException
);

It is possible to set the levels of errors reported to Flare as such:

Flare::reportErrorLevels(E_ALL & ~E_NOTICE); // Will send all errors except E_NOTICE errors
Previous topic Next topic