As announced in the release 3.2.0:
To detect accidental overwrites, cht-conf will generate two files - .snapshots/remote.json and .snapshots/local.json. These store the last known configuration on the server. The remote.json file should be commited with your configuration changes, and local.json should be added to the .gitignore since everyone's local environment is different. If changes are made to the configuration on the server using cht-conf or the App Management webapp without committing the remote.json file to your config repo, and then subsequently pulling the changes, then any attempt to upload configuration changes will be notified about the risk and prompted to either overwrite or cancel.
However, we only consider localhost as local.
|
if (parsed.hostname === 'localhost') { |
|
return 'local.json'; |
|
} |
With docker-helper & nginx-local-ip, now we can have local instances like this: https://192-168-0-3.local-ip.medicmobile.org:8443.
We might want to consider them as local so that remote.json is reserved for remote instances.
As announced in the release 3.2.0:
However, we only consider
localhostas local.cht-conf/src/lib/warn-upload-overwrite.js
Lines 29 to 31 in dae31f9
With docker-helper & nginx-local-ip, now we can have local instances like this:
https://192-168-0-3.local-ip.medicmobile.org:8443.We might want to consider them as local so that
remote.jsonis reserved for remote instances.