FlyEnv v4.15.3 Update Release Notes

🚀 New Features

1. Added RoadRunner Module

FlyEnv now includes a dedicated RoadRunner module for PHP application server workflows. You can install, detect, configure, and run RoadRunner directly from FlyEnv, then bind RoadRunner-backed projects into the standard project service experience.

This integration provides:

• RoadRunner Version Management: Discover, install, and manage RoadRunner releases from the Version Manager
• Standalone Service Mode: Start RoadRunner with a generated .rr.yaml fileserver configuration for quick local testing
• PHP Project Services: Manage RoadRunner projects from the project service view with start/stop, port, environment, log, and config workflows
• Project Presets: Quickly configure PHP Worker, Existing Config, Laravel Octane, Fileserver, or Custom command projects
• PHP Runtime Binding: Select a FlyEnv-managed PHP runtime for RoadRunner PHP Worker and Laravel Octane projects
• Config File Sync: Generate .rr.yaml files, detect existing RoadRunner configs, and keep project ports synchronized

2. Added Swoole CLI Module

FlyEnv now supports Swoole CLI as a first-class PHP runtime and project service module. You can install Swoole CLI versions, initialize the runtime files FlyEnv needs, and run Swoole-based PHP projects with purpose-built presets.

This integration provides:

• Swoole CLI Version Management: Discover, install, and manage Swoole CLI binaries across supported platforms
• Runtime Bootstrap: Prepare php.ini, php-fpm.conf, Composer, and CA certificate files for FlyEnv-managed Swoole CLI runtimes
• Project Presets: Run Native Swoole, Hyperf, EasySwoole, Laravel Octane, PHP Script, or Custom command projects
• Config Detection: Automatically detect common framework config files such as Hyperf server/routes, EasySwoole configs, Laravel Octane config, and server.php
• Project Service Workflow: Configure ports, startup commands, environment variables, config files, logs, and service lifecycle from the same project UI

3. Split PHP into PHP-FPM and PHP Project Services

The PHP experience has been reorganized into clearer responsibilities. PHP-FPM is now available as its own module for PHP runtime and FPM service management, while the PHP module now leads with PHP project service management.

This update makes PHP deployment workflows easier to understand:

• PHP-FPM Module: Manage PHP-FPM services and PHP runtime versions separately
• PHP Project Services: Start and stop PHP projects through the common project service workflow
• Cleaner Navigation: Keep PHP runtime/service management separate from PHP project deployment
• Complete PHP Deployment Coverage: FlyEnv now covers PHP, PHP-FPM, FrankenPHP, RoadRunner, and Swoole CLI deployment shapes in one desktop app

Thanks to @chunbo007 for the discussion! Discussion #694

4. Added ZincSearch Module

FlyEnv now includes a dedicated ZincSearch module for running the lightweight search engine locally. You can install ZincSearch, manage the service lifecycle, edit environment configuration, inspect logs, and open the ZincSearch UI directly from FlyEnv.

This integration provides:

• Service Management: Start and stop ZincSearch through the standard FlyEnv service workflow
• Version Management: Install and manage ZincSearch releases from GitHub
• Environment Configuration: Configure admin credentials, data path, bind address, port, and log level through zincsearch.env
• Log Access: View standard and error logs directly in the ZincSearch module
• Quick UI Access: Open the ZincSearch web UI using the configured host and port when the service is running

Thanks to @zzdboy for the feature request! Issue #440

🛠️ Improvements & Bug Fixes

5. Added Remarks to Installed Version Lists

Installed version lists now include a Remark column, making it easier to label local runtime versions and remember what each installed version is used for. Remarks can be edited directly from the installed list, are persisted locally, and are shown in service-related version management views.

This helps prevent accidental deletion or confusion when multiple versions of the same runtime are installed for different projects.

Thanks to @Y0n3er for the feature request! Issue #543

6. Fixed MariaDB 11.4+ / 12+ Startup Issue on Windows

Resolved a Windows startup failure affecting newer MariaDB builds that require PEM files for zero-configuration SSL and authentication key handling. FlyEnv now generates and supplies the required ca.pem, server-cert.pem, server-key.pem, private_key.pem, and public_key.pem files when needed, preventing MariaDB 12+ from failing to start because those files are missing.

7. Improved Cloudflare Tunnel Local Domain Binding

Cloudflare Tunnel local service bindings now support choosing HTTP or HTTPS per local domain rule. This lets each tunnel rule forward to the correct local protocol and helps avoid WordPress redirect issues caused by forcing the wrong protocol during local-to-public forwarding.

8. Fixed macOS Service Startup State

Resolved an issue on macOS where a service could remain stuck in the "starting" state after the startup command completed. Service state now settles correctly after startup succeeds or fails.

📦 Build & Transparency

All FlyEnv installation packages are built using GitHub Actions. You can verify the build process and download the artifacts directly from the following links:

• Global Build History: GitHub Actions

We welcome your continued feedback and bug reports via GitHub Issues

Enjoy the update!