Be sure to update the following values in your YAML file:
<your-namespace>
(two occurrences)<version>
- 4.x version you’re upgrading to<password>
- retrieved fromget-env
call above<secret>
- retrieved fromget-env
call above<admin-user>
- needs to be the same as used in 3.x - likelymedic
<uuid>
- retrieved fromget-env
call above<url>
- the URL of your production instance goes here (egexample.org
)<path-to-tls>
- path to TLS files on disk
Storage Configuration Notes:
The storage related values don’t need to be changed but here’s an explanation:
preExistingDataAvailable: "true"
- If this is false, the CHT gets launched with empty data.dataPathOnDiskForCouchDB: "data"
- Leave asdata
because that’s the directory we created above when moving the existing data.partition: "0"
- Leave as0
to use the whole disk. If you have moved data to a separate partition in a partitioned hard disk, then you’d put the partition number here.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified 12.12.2024: Migration from CHT 3.x on docker-compose to CHT 4.x on k3s (#1723) (54790cdb)