Enable a Block
Blocks are install-time switches, controlled per app by EVOLAYER_BASE_EXAMPLE_* flags read through config/evolayer.php. Enabling registers the block's routes and sidebar entry; disabling drops them while the shared prop key stays present.
The workflow
bash
# .env — flip the block's flag
EVOLAYER_BASE_EXAMPLE_ADMIN_INBOX=true
php artisan config:clear
php artisan route:clear
php artisan wayfinder:generate --with-form --no-interaction
npm run buildNote
Flags are per-install posture, not per-user feature flags. For rollout or A/B behaviour, reach for Laravel Pennant instead.
Checking what's on
The shared Inertia prop evolayer.base.examples lists every block key with its current state — the frontend never guesses.
Was this page helpful?
Source: xuple/evodevops/resources/js/pages/docs/evocraft/how-to/enable-a-block.tsx