SETTING — the settings a service reads

Raised by lemonfiber settings, and where a setting is read, set or cleared through the web API. A setting is a value a service reads, with a declared default and the operator’s value where one is recorded; a secret is never written or read back this way. See the commands.

Code	Severity	Exit	What it means	What to do
SETTING-1	error	5	No service in this stack reads a setting by that name, and it is not one of the core's own, so writing it would record a value nothing reads. Nothing was changed.	List the settings with lemonfiber settings.
SETTING-2	error	5	That name is a secret's. A secret is entered where it is first needed and replaced at the terminal, never written as a setting, so nothing was changed.	Replace it at the terminal with lemonfiber credentials --rotate.
SETTING-3	error	5	One name has one writer. That name is taken by the other of lemonfiber settings and lemonfiber config, so nothing was changed; the message names the command and the name that take it.	Run the command the message names.
SETTING-4	error	5	The value cannot be written as that setting: a setting is one line with no control character, and a core setting is held to the form its table names. Nothing was changed.	Give the value on one line, in the form the message names.
SETTING-5	error	1	The change answers a reading of the settings that has since moved, or a document it regenerates changed while it was being made. Agreeing to it now would be agreeing to something nobody saw, so nothing was changed; the message names what moved.	Read the change again, and answer the name it prints.
SETTING-6	advisory	1	The setting already holds what was asked for, so nothing was changed, and nothing needed to be.	Nothing to do. lemonfiber settings lists what each setting holds.

What each severity and each exit means is on every error by code, beside every other family.