Overview
Envloom stores global settings in~/.envloom/config.json. These settings control application behavior, service management, and system integration. All settings can be modified through the desktop UI’s Settings page or by directly editing the configuration file.
Changes to global settings take effect immediately and persist across application restarts.
Configuration File Location
The global configuration file is stored at:Available Settings
Auto-Start Services
Controls whether PHP-FPM, Nginx, and MariaDB services start automatically when Envloom launches.When enabled, all installed and configured services will start in the background on application launch, allowing immediate access to your local sites.UI Location: Settings > Auto-start services on app launch
Auto-Update
Enables automatic hourly checks for runtime updates (PHP, Node.js, MariaDB).When enabled, Envloom checks for new runtime versions every hour and displays an Update button in the UI when newer versions are available. The actual update is never performed automatically—you always control when to update.UI Location: Settings > Check for updates hourly
Start with Windows
Configures Envloom to launch automatically when Windows starts.When enabled, Envloom creates a registry entry in
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run to start the application at login.UI Location: Settings > Start with WindowsThis setting requires elevation (UAC) to modify the Windows registry. You’ll be prompted for administrator access when toggling this option.
Start Minimized
Controls whether Envloom starts in the system tray instead of showing the main window.When enabled and combined with Start with Windows, Envloom launches silently to the system tray, keeping services running in the background without showing the UI.UI Location: Settings > Start minimized to tray
Complete Configuration Example
~/.envloom/config.json
Legacy Compatibility
autoStart (Legacy)
autoStart (Legacy)
Older versions of Envloom used When Envloom loads a configuration with the legacy
autoStart instead of autoStartServices. The configuration system maintains backward compatibility:autoStart key, it automatically migrates to autoStartServices. Future saves will use the new key name.Managing Settings via UI
All global settings can be managed through the desktop application:- Launch Envloom
- Navigate to Settings in the sidebar
- Toggle the desired options
- Changes save automatically
Managing Settings via CLI
While the CLI doesn’t currently expose a dedicated settings command, you can directly edit the configuration file:Accessing Settings in Code
For developers extending Envloom, settings are exposed via theAppSettings struct:
src-tauri/src/domain/models.rs
~/.envloom/config.json via the infrastructure/persistence.rs module.
Related Configuration
File Paths
Learn about Envloom’s file structure and important directories
Per-Site Config
Configure runtime versions and settings per individual site