configuration.local_read_failed

The .env.local file is there, but it couldn't be read: it is a folder, or you aren't allowed to read it.

Area 14, Tools; not declinable; the next step is usually the human's.

Why Jadpo refuses it

.env.local holds this machine's values for the settings in config.jadpo. When it is there but can't be read, carrying on without it would start the app with other values, or report settings as missing that the file sets, so every command that reads it stops instead and says why reading failed.

Jadpo won't fix it for you: making the file readable or removing it changes your files, and only you know whether what is there should be kept.

What it looks like

A project's config.jadpo declares a secret mail_api_key, and .env.local is a folder:

mkdir .env.localjadpo config check

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides what happens to a file that may hold your secrets.

A file you aren't allowed to read, such as one written with sudo, is refused the same way, with Permission denied as the reason.

How to fix it

If it is a folder made by mistake, remove it, then store the values at the prompt:

rmdir .env.localjadpo config set mail_api_key

The settings read from a new, ordinary .env.local that only you can read.

If it is a file you aren't allowed to read, make it yours again:

sudo chown "$USER" .env.local

The commands read the values it holds, and jadpo dev starts with them.

Related

• Values on your machine and in production
• Setting a value: jadpo config set
• Checking values: jadpo config check