Workflows

Migrate from Enlightn

LaraBeacon keeps the public analyzer architecture familiar while updating package names, namespaces, commands, configuration, and current Laravel support.

1. Capture the current result

Run your existing Enlightn setup and save the report. Treat it as migration evidence, not as a baseline to copy blindly.

2. Replace the package

composer remove enlightn/enlightn
composer config repositories.larabeacon vcs https://github.com/A-Baer/LaraBeacon
composer require --dev baer-software/larabeacon:dev-main

3. Publish and review configuration

php artisan vendor:publish --tag=larabeacon

Review custom analyzer class names, namespace references, exclusions, environment variables, and ignored errors. Do not overwrite an existing application configuration without comparing it first.

4. Update commands

Enlightn	LaraBeacon
`php artisan enlightn`	`php artisan larabeacon`
`php artisan enlightn:baseline`	`php artisan larabeacon:baseline`
`config/enlightn.php`	`config/larabeacon.php`

5. Compare findings

Run LaraBeacon with details, reconcile expected differences, and create a fresh baseline only after the new report has been reviewed. Current Laravel behavior may make previously skipped checks applicable.