veld

# Veld Veld orchestrates local dev environments. It starts services from `veld.json`, wires dependencies, and gives each service an HTTPS URL like `https://frontend.my-feature.myproject.localhost`. ## Version Check Installed: !`veld -V 2>&1` If the output above shows "command not found" or "No such file", veld is not installed. Guide the user through installation — see [reference/install.md](reference/install.md). Do NOT attempt to run any `veld` commands until it is installed. If the installed version is older than what `compatibility` requires, tell the user: "This project requires a newer veld. Run `veld update` to upgrade." ## Live State ### Configuration !`veld config 2>&1` ### Nodes & presets !`veld nodes 2>&1` !`veld presets 2>&1` ### Active runs !`veld runs 2>&1` ## CLI !`veld --help 2>&1` Run `veld <subcommand> --help` for flags and options. ## Node actions A node can declare **actions** — shell commands that the CLI and dashboard expose generically. Veld injects the node's live outputs so the rotating clone port and password never have to be copied by hand. ```jsonc // in veld.json, under a node: "database": { "variants": { "dblab": { /* … */ } }, "actions": [ { "name": "psql", "label": "psql", "description": "Open a psql shell to the DB clone", "requires_outputs": ["DB_HOST", "DB_PORT", "DB_NAME", "DB_USER", "DB_PASS"], "command": "PGPASSWORD=$DB_PASS psql -h $DB_HOST -p $DB_PORT -U $DB_USER $DB_NAME" } ] }...