Contradicting information about `/config` on caddyserver.com and hub.docker.com

[stupid-stove]

On https://hub.docker.com/_/caddy it is stated: "While it's not necessary to persist the files stored in the configuration directory, it can be convenient."

However https://caddyserver.com/docs/conventions#configuration-directory (which is linked on the docker page) states: "It is crucial that this directory is persistent and writeable by Caddy."

Those two sentences seem to contradict each other. If this is intended, consider adding a disclaimer that this is only true for the docker version to avoid confusion.

[francislavoie]

I would say both are misleading. It's only actually relevant if you use caddy run --resume. If you don't (vast majority of people don't) then you can omit it. But really, it's basically no cost to just have one line in your docker-compose to persist it just in case you do need it later or w/e.

[stupid-stove]

@francislavoie Thanks, that makes sense. I'll probably open an issue in the caddy docs later, as I think this could have been written clearer.