Docker image does not distiguish data and config folders

[nettnikl]

What happened?

Splitting data and config from each other is widely considered a best practice. However, for this /app/data/ has to be used not for config files.

What did you expect to happen?

Mounting possible with data as rw and config as ro.

    volumes:
      - ./zigbee2mqtt-config/configuration.yaml:/app/data/configuration.yaml:ro
      - ./zigbee2mqtt-config/custom-adapter.js:/app/data/custom-adapter.js:ro
      - ./zigbee2mqtt-data:/app/config:rw

But it is required to ensure, the start script does not copy stuff around (especially not only in the initial case), so if the config is changed afterwards, the change is reflected.

EDIT: #4697 includes a similar discussion.

Zigbee2MQTT version

latest

[Hypfer]

To my understanding, the config file needs to be writable so that configuration via the frontend works.

is widely considered a best practice

Any source on that? And why does that matter? Sounds like just an opinion to me

[nettnikl]

Well, any best-practise could be considered 'an opinion' - but i'd argue that in most OS' programs are generally pushed to split those.
For security (in cloud env e.g. making configs readonly) and maintanability (easy data resets with losing configs). E.g. /etc and /bin or the AppData and Programs directories.

[nettnikl]

A config file the program has to write to sounds like an unusual design choice to me. Not inherently a bad one, but for me an non cloud friendly one. For example, I like to reset my systems by deleting the data, while keeping the settings - similar to what MS started to offer for soft resetting Windows and what docker containers generally do on recreation (unless you specified to keep the data at a specific location via the volumes).

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[nettnikl]

This is very disappointing.

[nettnikl]

I'd be thankful if i could get any reason for why this was closed. If it is not planned, i'm sure you have a good reason not to, i'd be interested to hear about it.