Managing Sites

Burrow serves your local applications using two methods: Parked Directories and Linked Paths.

Parked Directories

A Parked Directory is a folder where Burrow monitors all subdirectories and automatically serves them as local websites. By default, Burrow creates a Burrow folder inside your user profile. Any child folder within this directory is instantly available in your browser:

• %USERPROFILE%\Burrow\laravel-app resolves to http://laravel-app.local
• %USERPROFILE%\Burrow\wordpress resolves to http://wordpress.local

Linking Directories

If your projects live outside the default park directory (e.g., D:\Projects\ecommerce), you can link them manually:

1. Open the Burrow GUI, go to the Projects page, and click Link Project.
2. Select the directory, choose a domain, and assign the PHP and Node.js versions.
3. Alternatively, navigate to the folder in your terminal and run:

   burrow link ecommerce.local
   

Framework Auto-Detection

Burrow scans linked folders to automatically identify the appropriate Nginx configuration driver:

• Laravel: Detected via artisan. Burrow automatically configures environment settings and reads .env database values.
• WordPress: Detected via wp-config.php or wp-config-sample.php.
• CodeIgniter 4 / 3: Detected via spark or application/config/config.php.
• Symfony: Detected via symfony.lock.
• Drupal / Magento: Detected via core files.
• Generic Public / Basic: Serves the folder using a standard document root (e.g. public/ directory if present).

Explorer Integration

To help organize your projects, Burrow updates folder icons in Windows Explorer based on the detected framework (e.g., displaying the Laravel or WordPress logo on the directory). This is handled via standard Windows desktop.ini configurations.