これは旧バージョンです。最新版は4.20.2です。 FlyEnv 4.20.2 · リリース日:
インストーラーファイル 4.17.2
| アーキテクチャ | 種類 | インストール範囲 | ファイルサイズ | ダウンロード | SHA256 |
|---|---|---|---|---|---|
| 64ビット | EXE（NSIS） | 現在のユーザー | — | github.com | VirusTotal |
| 64ビット | EXE（NSIS） | すべてのユーザー | — | github.com | VirusTotal |
リンクとSHA256はWindows Package Managerのコミュニティマニフェストから取得しています。実行する前に、ダウンロードしたファイルのハッシュを照合してください。
リリースノート
FlyEnv v4.17.2 Update Release Notes
🚀 New Features
1. Added ClickHouse Support
FlyEnv now includes a dedicated ClickHouse module for installing, managing, configuring, and monitoring local ClickHouse database servers on macOS and Linux.
This integration provides:
- Version Management: Download and manage ClickHouse releases directly from FlyEnv
- Service Controls: Start and stop installed ClickHouse versions alongside your other local services
- Configuration and Logs: Edit the config.xml and users.xml files and review server, startup, and error logs from the module
- Built-In Browser UI: Open a managed CH-UI browser interface for a running ClickHouse server
Issue #774
2. Added Temporal Server Support
FlyEnv now includes a dedicated Temporal module for running a local Temporal Server. You can download and manage server versions, edit the generated server configuration, inspect logs, and open the Temporal Web UI when you need to explore workflows and namespaces in a browser.
Issue #730
3. Added Temporal CLI Support
A separate Temporal CLI module is now available for local development workflows. It manages the official Temporal CLI and its temporal server start-dev development server, with configurable ports, local database settings, logs, and direct access to the built-in Web UI.
Issue #730
4. Control Startup Groups from the Tray Menu
Startup Groups are now displayed in the FlyEnv tray menu, ahead of individual services. You can start or stop a saved group directly from either tray style, making it easier to switch an entire project environment without opening the main window.
Issue #782
🛠️ Improvements & Bug Fixes
5. Improved Windows Privileged Operations and Helper Recovery
Windows users can now choose the elevation method used for operations that require administrator permission: the persistent FlyEnv Helper or standard UAC prompts. FlyEnv continues to use the Helper by default, while UAC offers a practical alternative for supported operations on systems where the Helper cannot be installed or used.
If Helper installation fails, FlyEnv now automatically switches to UAC so supported privileged actions remain available instead of being blocked by the failed Helper setup.
Issue #756 Issue #797
📦 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!
