configuration.local_write_failed

Saving a value in .env.local failed, usually because the project's folder can't be written.

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

Why Jadpo refuses it

jadpo config set saves a value by writing a new file only you can read beside .env.local, then putting it in the old one's place, so a half-written file never holds your secrets. When that can't be done, it stops and says why, and .env.local is as it was.

Jadpo won't change the folder's permissions for you: who may write in it is a decision about your machine, not about the app.

What it looks like

A project's config.jadpo declares a secret mail_api_key, and the project's folder is read-only. Storing a value at the prompt:

chmod a-w .jadpo config set mail_api_key

? Enter MAIL_API_KEY hiddenerror: `.env.local` couldn't be saved  reason: Creating it failed: Permission denied (os error 13).  next: Check that the project's folder is writable, then run the command again (human)  rule: configuration.local_write_failed  help: https://jadpo.dev/docs/errors/configuration.local_write_failed

(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 who may write in the project's folder.

How to fix it

If the folder should be writable, let yourself write to it, then store the value again:

chmod u+w .jadpo config set mail_api_key

The value is saved in .env.local, which git ignores.

If the folder should stay read-only, give the value in the environment instead, as a server does:

export MAIL_API_KEYread -rs MAIL_API_KEYjadpo dev

The environment wins over .env.local, and nothing is written.

Related

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