Skip to content

Command Palette

Search for a command to run...

Version 1.2.0

Dashboard configuration management

Edit phelix.yaml with synchronized visual and YAML modes, agent validation, revision checks, and atomic saves.

Edit configuration

Open an application in the dashboard and choose Configuration. The visual builder and YAML editor share one draft. Fields come from the connected CLI's configuration schema. The editor provides highlighting, search, formatting, and diagnostics; valid YAML changes appear in the builder.

If phelix.yaml is missing, prepare and review a draft before creating it. Opening the page does not create a file. Restricted categories remain read-only, and unknown fields are retained when editing.

Validate and save

The browser checks YAML syntax and the owning monitor validates the draft with the CLI's rules. Validation runs no build, hook, or job and does not save. Saving checks the loaded revision and replaces valid changed content atomically.

Failed saves retain the draft. A conflict requires reviewing the latest file before reloading; leaving with unsaved changes requests confirmation. After a timeout, refresh metadata or safely retry the same content to establish the outcome.

Terminal
phelix config lint
phelix config schema

Apply saved settings

Saving changes the project file without restarting or deploying the application. The next applicable build or lifecycle operation reads its settings, with explicit CLI overrides still taking precedence.

Permissions and boundaries

Viewing and managing settings require their respective application permissions and a connected owning monitor. Additional category permissions apply. Security reporting consent remains local; runtime environment values and secret-store values are never retrieved by configuration management.

The document limit is 512 KiB. Symbolic links and unsafe YAML structures are rejected. External editors must honor the shared file lock for strict simultaneous-write protection.