Settings & Configuration
Customize FlareDeck to fit your workflow
Theme
FlareDeck supports three theme modes:
- Light — Bright interface for well-lit environments
- Dark — Reduced eye strain for extended sessions
- System — Automatically matches your OS theme preference
Change the theme from Settings → Appearance.
cloudflared Binary Path
By default, FlareDeck looks for cloudflared in your system PATH. If cloudflared is installed in a non-standard location, you can set the path manually:
- Open Settings.
- Under cloudflared Path, click Browse or enter the full path to the binary.
- FlareDeck validates the binary and displays the detected version.
# Default locations
C:\Program Files\cloudflared\cloudflared.exe # Windows (winget)
C:\Users\<user>\scoop\apps\cloudflared\current\cloudflared.exe # Windows (scoop)If you update cloudflared to a new version, FlareDeck will detect the change automatically on next launch.
Default Settings
FlareDeck uses sensible defaults that work for most development scenarios:
| Setting | Default | Description |
|---|---|---|
| Theme | System | Matches OS preference |
| cloudflared path | Auto-detect | Searches PATH |
| Log buffer size | 1000 lines | Max lines kept in memory per profile |
| Auto-scroll logs | Enabled | Log viewer follows new output |
Backup Configuration
FlareDeck's state is stored locally. To back up your configuration:
- Tunnel configs — Copy
~/.cloudflared/*.ymlfiles. These contain your ingress rules and tunnel settings. - Tunnel credentials — Copy
~/.cloudflared/*.jsonfiles. These are required to run named tunnels. - Certificate — The
~/.cloudflared/cert.pemfile is your account authorization.
Treat credential files and cert.pem as secrets. Never commit them to version control or share them publicly.
To restore on a new machine, place these files in ~/.cloudflared/ and launch FlareDeck — it will discover and import the existing tunnels as profiles.