project_settings

ru.layero/layero · Verify this server

Build settings of a project: read them, or change them without the dashboard — the way out when detection guessed wrong (wrong folder, wrong type, wrong command). `get` returns `settings` (what is saved on the project; null — not set, the platform decides), `resolved` (what the next build will actually use, per field: `value`, `source`, `policy`) and `last_build` (what the latest ready build was really built with). Precedence is `layero.json` in the repository > project settings > detection > framework default: a field with `policy: "locked_by_file"` is set by `layero.json`, and changing the project setting will not change the build — edit the file instead. `update` CHANGES HOW THE PROJECT IS BUILT — ask the person first unless they asked for exactly this change. Prefer `layero.json` in the repository for anything that should live with the code; use this tool for what the file cannot hold (`root_directory`, `project_type`) and for projects you cannot push to. Nothing is rebuilt by the update itself: apply it with `retry_deploy(redeploy=true)` or a push.