Hi Jibril -
Yes exactly how bench config commands apply can be confusing, these clues may help:
frappe@ubuntu1804lts:~/frappe-bench$ bench --help | grep config
config Change bench configuration
set-config Insert/Update a value in site_config.json
show-config print configuration file
To turn off auto_update try this:
frappe@ubuntu1804lts:~/frappe-bench$ bench set-config auto_update off
frappe@ubuntu1804lts:~/frappe-bench$ find . -name ‘.json’ | xargs grep auto_update
./sites/common_site_config.json: “auto_update”: false,
./sites/site1.local/site_config.json: “auto_update”: “off”,
frappe@ubuntu1804lts:~/frappe-bench$ bench set-config auto_update on
frappe@ubuntu1804lts:~/frappe-bench$ find . -name '.json’ | xargs grep auto_update
./sites/common_site_config.json: “auto_update”: false,
./sites/site1.local/site_config.json: “auto_update”: “on”,
Whereas here’s a bench config command example:
frappe@ubuntu1804lts:~/frappe-bench$ bench config dns_multitenant true
frappe@ubuntu1804lts:~/frappe-bench$ find . -name ‘*.json’ | xargs grep dns_multitenant
./sites/common_site_config.json: “dns_multitenant”: true,
Note that currentsite.txt specifies the site where the bench will apply the change:
frappe@ubuntu1804lts:~/frappe-bench$ cat sites/currentsite.txt
site1.local