Skip to content

Set what every machine inherits

Every machine in an account starts from one set of settings. Decide them once, and each machine runs under them until that machine sets its own.

In Machinery, open Settings. The page says what every machine in the account gets unless it sets its own, and it has six sections: Storage, Power, Memory, Reachability, Snapshots and Setup.

Each section saves the whole domain at once, so a save that fills one card keeps the account’s decisions beside it.

One verb per domain, and each one replaces its whole domain:

CommandSets
account-settings set-powerthe idle alarm, auto-stop, and the alarm for a stop or start that did not take
account-settings set-storagethe disk alarm and the volume growth bounds
account-settings set-memorythe memory pressure alarm and the out-of-memory alarm
account-settings set-reachabilitythe offline alarm and whether machines answer over HTTP at their Deployport domain
account-settings set-snapshotsthe snapshot schedule and the alarm for a restore that could not place its volume
account-settings set-setupthe failed step alarm, and the steps every new machine runs

A setter replaces what the account stores, so name every setting the account should keep, every time. A setting you leave out stops being the account’s own and Machinery’s default decides it, and --clear unsets the whole domain in one call.

The write prints the settings the account now has, so what changed is on screen rather than worked out.

To turn auto-stop on for every machine in the account, this names the three power settings the account should decide:

Terminal window
deployport machinery account-settings set-power --auto-stop-enabled true --idle-alarm-enabled true --idle-alarm-idle-for 30m

Let a machine stop itself names the power settings and what each one decides.

A machine’s page carries its own copy of all six domains, each in the tab that answers its question: Power for the idle alarm and auto-stop, Storage for the disk alarm and volume growth, Memory for the pressure alarms, Snapshots for its schedule, Network for reachability, and Setup for its steps.

Whether a machine answers over HTTP at its Deployport domain is the account’s alone, so it is not on a machine’s page.

From the CLI there is one verb for the domain a machine overrides most, which is power:

Terminal window
deployport machinery set-power-settings <machine-id> --auto-stop-enabled false
deployport machinery set-power-settings <machine-id> --clear

It replaces the whole domain the same way, and --clear unsets every power setting the machine carries so the account decides them again.

The longest a developer may keep a machine running past an idle stop is the account’s alone. A ceiling a machine may raise is not a ceiling, so no machine sets it.

Terminal window
deployport machinery settings <machine-id>

One row per setting: the value in effect, what set it, and whether this machine may change it. SET BY reads default for what Machinery ships, account for the account’s value, and machine for the machine’s own.

The values are resolved when you read them, so this is what the machine runs with now rather than a copy of anything stored.

A setting is named by a path: the domain, the slot and the setting, such as power.autoStop.headsUpSeconds. deployport machinery settings <machine-id> prints those paths, and the console’s Settings page and a machine’s own tab set the same settings under the section that matches the domain.