Skip to content
GurtOS

Where a system update stands

GET
/update
curl --request GET \
  --url http://127.0.0.1:7700/api/update \
  --header 'Authorization: Bearer <token>'

How this computer updates, read from what box-update leaves behind. Only an installed image has update slots A and B. A checkout installed with core/install.sh, or the install disc running live, has none, and its state is unknown. Nothing looks for updates by itself yet, so automatic is always false and Settings autoUpdate and updateChannel change nothing. See Update and roll back.

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”

The version and the update state.

Media typeapplication/json
object
version
required
string
build
required
string
state
required

unknown off an installed image. ready: a new system is written and waits for a restart. trial: it is running on trial. rolledBack: the last update did not start or was rolled back.

string
Allowed values: current ready trial rolledBack unknown
slot

The slot this computer booted

string
Allowed values: a b
last

The last result line box-update wrote.

string
lastAt
string
install
required
string
Allowed values: image disc checkout
slots
required

Whether this install has update slots A and B.

boolean
automatic
required

Nothing looks for updates by itself yet.

boolean
default

The slot the boot menu starts by default.

string
Allowed values: a b
other

The other slot.

object
slot
string
Allowed values: a b
unfinished

A write to it did not finish

boolean
trial

The slot that is on trial.

string

Examples

{
  "version": "0.1.0",
  "build": "3c4626c",
  "state": "current",
  "slot": "a",
  "install": "image",
  "slots": true,
  "automatic": false,
  "default": "a",
  "other": {
    "slot": "b"
  }
}