Development Environment Setup

This document covers setting up a local development environment for working on the laravel-boost-copilot-cli package itself. It explains the required dependencies, Composer scripts, Orchestra Testbench workbench configuration, and the package development workflow.

For information about installing and using the package in your Laravel application, see Installation. For testing the package, see Testing with Orchestra Testbench.

Purpose and Scope

This page is for developers who want to:

• Contribute to the laravel-boost-copilot-cli package
• Modify or extend the package locally
• Test package functionality in isolation
• Understand the package's development toolchain

It does not cover end-user installation or configuration, which are documented in the Getting Started chapter.

Prerequisites

The package requires specific PHP and Laravel versions as defined in composer.json11-14:

Requirement	Version Constraint
PHP	^8.2
illuminate/support	^12.30 || ^13.0
laravel/boost	^2.0

Development dependencies include testing and quality assurance tools defined in composer.json16-21:

Tool	Purpose	Version
orchestra/testbench	Package development environment	^10.6
pestphp/pest	Testing framework	^4.1
pestphp/pest-plugin-laravel	Laravel-specific test features	^4.0
laravel/pint	Code formatting	^1.25
mockery/mockery	Mocking framework	^1.6

Sources: composer.json11-21

Development Workflow Overview

Title: Initial Setup and Development Workflow

The development environment is automatically configured through Composer's post-autoload-dump hooks defined in composer.json63-66 These hooks execute three scripts sequentially:

1. clear - Purges skeleton files
2. prepare - Discovers packages
3. build - Builds the workbench environment

Sources: composer.json63-76 testbench.yaml23-27

Composer Scripts Reference

The package defines several Composer scripts for common development tasks in composer.json53-76:

Testing Scripts

Title: Testing Script Execution Flow

Script	Command	Purpose
test	pest --compact	Run test suite with compact output
test:coverage	pest --compact --coverage --coverage-clover build/logs/clover.xml	Run tests with code coverage report

Sources: composer.json54-55

Code Quality Scripts

Script	Command	Purpose
lint	pint	Format code according to Laravel standards
test:lint	pint --test	Check code formatting without modifying files

Sources: composer.json56-61

Workbench Management Scripts

Title: Workbench Management Script Dependencies

Script	Command	Purpose
clear	testbench package:purge-skeleton --ansi	Remove skeleton files from workbench
prepare	testbench package:discover --ansi	Discover and register packages
build	testbench workbench:build --ansi	Execute build steps from testbench.yaml
serve	testbench serve --ansi	Start development server (with timeout disabled)
boost	testbench boost:install --no-interaction --ansi	Run boost:install in Testbench environment

The serve script includes Composer\Config::disableProcessTimeout to prevent Composer from timing out the long-running server process composer.json71-75

Sources: composer.json62-75

Package Autoloading Configuration

The package defines PSR-4 autoload mappings for both production and development code:

Title: Package Autoload Namespace Mapping

Directory	Namespace	Environment	Purpose
src/	Revolution\Laravel\Boost	Production	Package source code
tests/	Tests	Development	Test suite
workbench/app/	Workbench\App	Development	Test application code
workbench/database/factories/	Workbench\Database\Factories	Development	Model factories
workbench/database/seeders/	Workbench\Database\Seeders	Development	Database seeders

Sources: composer.json23-34

Orchestra Testbench Workbench Configuration

The testbench.yaml file configures the workbench environment used for package development and testing.

Workbench Build Process

Title: Workbench Build Sequence

The build process is defined in testbench.yaml23-27 and executes four steps:

Step	Command	Purpose
1	asset-publish	Publish Laravel framework assets
2	create-sqlite-db	Create SQLite database file
3	db-wipe	Clear existing database data
4	migrate-fresh	Run all migrations

Sources: testbench.yaml23-27

Workbench Feature Configuration

The workbench is configured with specific features enabled or disabled in testbench.yaml12-22:

Feature	Status	Purpose
web routes	✓ Enabled	Discover web routes
api routes	✓ Enabled	Discover API routes
commands	✓ Enabled	Discover Artisan commands
factories	✓ Enabled	Discover model factories
components	✗ Disabled	Blade components not needed
views	✗ Disabled	View discovery not needed
install	✓ Enabled	Run package installation
health	✗ Disabled	Health checks disabled

The workbench start page is configured to '/' and migrations are loaded from workbench/database/migrations testbench.yaml6-13

Sources: testbench.yaml12-22

Database and Migration Configuration

Title: Database and Migration Setup

Configuration	Value	Purpose
Migrations Path	workbench/database/migrations	Directory containing test migrations
Database Seeder	Workbench\Database\Seeders\DatabaseSeeder	Seeder class for test data
Database Type	SQLite	Lightweight database for testing

Sources: testbench.yaml6-10

Asset and Storage Synchronization

The workbench configuration includes asset publishing and storage synchronization:

Configuration	Setting	Purpose
Assets	laravel-assets	Laravel framework assets to publish
Storage Sync	storage → workbench/storage (reverse)	Bidirectional storage directory sync

The reverse: true setting in testbench.yaml33 enables bidirectional synchronization between the package's storage directory and workbench/storage.

Sources: testbench.yaml28-33

Development Directory Structure

Title: Package Directory Structure for Development

Directory	Namespace	Purpose
src/	Revolution\Laravel\Boost	Package source code
src/CopilotCli.php	-	Main agent implementation
src/CopilotCliServiceProvider.php	-	Service provider registration
tests/Feature/	Tests\Feature	Feature test suite
workbench/	-	Testbench application root
workbench/app/	Workbench\App	Test application classes
workbench/database/	-	Test database structure
vendor/	-	Composer dependencies

Sources: composer.json23-34 testbench.yaml1-33

Service Provider Registration

The package automatically registers its service provider through Laravel's package auto-discovery mechanism defined in composer.json45-50:

Title: Service Provider Auto-Discovery

The CopilotCliServiceProvider class is automatically discovered and registered by Laravel applications that include this package. This configuration is in the extra.laravel.providers section of composer.json.

Sources: composer.json45-50

Quick Start Commands

To begin developing on the package:

After running composer install, the environment is ready for development. The workbench provides a full Laravel application context for testing package functionality.

Sources: composer.json53-76 testbench.yaml1-33