GurlGurl
Home
Docs
Home
Docs
  • Documentation

    • Documentation
    • Settings
    • Environments
    • Variables
    • Run history
    • Keyboard shortcuts
    • CLI

Environments

Environments are named bundles of .env files. Switching environments swaps which files are loaded into hurl as --variables-file flags, and re-tints the titlebar so you always know which one is active.

Defining environments

In settings.toml:

[[environment]]
name  = "Beta"
color = "#5E81AC"
files = [".env/.env", ".env/.beta.env"]

[[environment]]
name  = "Production"
color = "#BF616A"
files = [".env/.env", ".env/.production.env"]
KeyRequiredNotes
nameyesShown in the dropdown. Must be unique across the array.
colornoHex string. Used for the swatch + titlebar tint. Defaults to a palette color when omitted.
filesnoList of .env files, in layering order — later files override earlier ones. Paths are relative to the workspace root.

Switching

  • Toolbar dropdown — click the environment pill, top-right.
  • ⌥1–9 — jump directly to the Nth environment (matches the order in settings.toml).
  • The active environment's color tints the titlebar so the current context is always visible.

Auto-discovery

The first time you open a workspace, Gurl picks the environment config for you:

  • If settings.toml (or settings.local.toml) already defines environments, those are used as-is.
  • Otherwise, any .env* files in the workspace get seeded into one environment each, using a friendly name derived from the filename.

After that first open, Gurl steps back — adding or removing .env* files later won't auto-create or remove environments. Edit settings.toml (or use the toolbar dropdown → New Environment…) to manage them yourself.

Prev
Settings
Next
Variables