Change a deploy’s settings
Changed onAny of branch, root_dir, framework, port, health_path, install_cmd, build_cmd, start_cmd, auto_deploy; an Ingot repo also at (a changeset id, or null for the newest on main), and its branch stays main. The name cannot change. Changes apply from the next deploy; a port change moves its app and public URL and builds the live commit again. When the computer already has a URL on the new port, the one the deploy made goes and that build takes the one already there.
Request
- Base URLhttps://www.orgo.ai
- AuthHTTP bearer
Path parameters
Computer id.
Deploy project id.
Request body
Response
Changed.
Example response
{
"repo": "acme/web",
"ingot_repo": "0b6f4c7e-2d1a-4c3b-9e8f-7a6b5c4d3e2f/notes"
}Changes
- info
added the non-success response with the status
- info
- breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - warning
added the new
ingotenum value to theresponse property for the response status - info
added the new optional request property
- info
added the optional property
/////to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- breaking