CONFIG — your settings

Raised when the settings file cannot be read, written, or kept anywhere, and by the doctor where a file or a service holding credentials is open to somebody it should not be.

Code	Severity	Exit	What it means	What to do
CONFIG-1	error	5	Your settings exist and could not be read. Nothing has been changed — lemonfiber will not guess at settings it cannot read.	Check the file is readable. The message names its path.
CONFIG-2	error	1	Your settings could not be saved. The change was not made and your existing settings are untouched.	Check the location is writable and has space.
CONFIG-3	error	1	There is nowhere to keep settings, because setup has not chosen a location yet.	Run lemonfiber setup.
CONFIG-4	warning	1	A file holding a credential can be read by somebody other than its owner. Nothing has been changed — this is the doctor reporting what it found.	Take the permissions back to their owner. The message names each file.
CONFIG-5	error	1	Your settings were written by a newer lemonfiber than the one running, so this build will not write over them. Nothing has been changed — an older build writing over a newer one's settings leaves a file neither version can make sense of, and no way back to the one you had.	Run the newer lemonfiber, or take this one forward with lemonfiber update self. The message names both versions.
CONFIG-6	error	1	A value could not be saved because it has a line break in it. Nothing has been changed — the settings file holds one setting per line, so the rest of the value would have been read as settings you never chose.	Check where the value came from, and set it to a single line. The message names the settings file.
CONFIG-8	warning	1	Your overlay is merged over the project lemonfiber writes, last, and changes the services it names. Nothing in it was held to what lemonfiber checks a service against, so what those services can reach and do is yours to vouch for. Nothing has been changed — this is the doctor reporting what it found.	Keep the overlay to what the services need, or move a change into the stack's own settings where one says it. The message names the overlay and each service it changes.
CONFIG-9	warning	1	A Compose file is still named under LEMONFIBER_OVERLAY, which lemonfiber no longer reads: the overlay is the one file overlay.yml in its configuration directory. Whatever the named file changed is not applied.	Move the named file to overlay.yml in lemonfiber's configuration directory, then remove the LEMONFIBER_OVERLAY line from the settings file. The message names both paths.
CONFIG-10	warning	1	lemonfiber runs the one project it generates from the stack's manifest and reads none of the stack's own Compose files. A file named here is one somebody changed, or one a stack of its own still carries, and whatever it says is not applied.	Move whatever the file changed into overlay.yml in lemonfiber's configuration directory, then delete the file. The message names each one.
CONFIG-11	warning	1	A service that belongs to whoever claims it first is not held with the credential lemonfiber minted for it: nobody holds it, so whoever reaches it first can take it; somebody else holds it; or it could not be asked. Nothing has been changed — this is the doctor reporting what it found.	Run lemonfiber seed to claim a service nobody holds, or lemonfiber reset where lemonfiber claimed it before. Where somebody else holds it and that was not you, reset its configuration and run lemonfiber seed. The message names the service and the secret lemonfiber holds for it.

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