Lataa FlyEnv 4.18.1

FlyEnv v4.18.1 Update Release Notes
🚀 New Features
1. Added Tomcat Application Mappings
Tomcat sites can now map application directories or WAR files to explicit context paths while creating or editing a site. FlyEnv validates the mapping, writes the required Tomcat Context descriptors, and keeps the generated configuration synchronized when the site changes.
This makes it possible to serve multiple applications from one Tomcat site using paths such as /, /api, or /admin without manually maintaining Tomcat XML files.

2. Added Configurable PHP FastCGI Worker Counts on Windows
Windows PHP FastCGI installations can now set the number of php-cgi workers for each installed PHP version. Choose an integer from 1 to 64 in FlyEnv; restarting a running PHP service applies the updated count.
This gives local PHP projects a supported way to tune concurrency when several sites or heavier development workloads are running at once.
Issue #830

3. Added Persian Language Support
FlyEnv is now available in Persian (fa). The new locale covers the application's built-in translation catalog and is selectable from the language settings.
Thanks to @Nitron2020 for the contribution! Pull Request #829

4. Added AI CLI Session Quick Actions
The session pages for Antigravity, Claude Code, Codex, GitHub Copilot CLI, Kimi, and OpenCode now provide quick actions for each working directory. Start a new AI CLI session directly in that directory, or resume its most recent session with one click.
This makes it faster to return to the right project context without manually opening a terminal, changing directories, and entering the CLI command.

🛠️ Improvements & Bug Fixes
5. Improved Windows Helper and Data Directory Initialization
FlyEnv now coordinates Windows Helper startup with data-directory initialization more reliably. When a new installation needs elevated access to create or repair its data location, FlyEnv can recover permissions and retry the operation before dependent setup continues.
This improves first-run reliability for Windows users who previously could not start using FlyEnv because its data directory or Helper had not initialized correctly.

6. Fixed Rust Installation on Windows
Resolved a Windows installation issue that could leave downloaded Rust archives in an invalid layout. FlyEnv now unpacks the official archive through a staging directory and installs its expected root directory correctly.

7. Removed NVM and FNM Support on Windows
FlyEnv no longer detects or operates the external NVM and FNM Node.js version managers on Windows. Managed Node.js versions continue to work through FlyEnv's built-in installation workflow, while removing this integration prevents the NVM startup popup reported by affected users.
Issue #831

8. Fixed Windows Tray Menu Click Behavior
The Windows modern tray menu now opens from a right-click only. Double-clicking the tray icon opens the main FlyEnv window without also displaying the quick-action menu.
Issue #831

9. Fixed macOS Alias PATH Entries
Resolved an issue where editing a FlyEnv alias on macOS could write a stray quote into the PATH export in .zshrc. Alias setup now parses existing path entries safely and preserves a valid shell configuration.
Issue #832

📦 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!