Explore the process of migrating to using PIH config as the CHT demo config.

[antonykhaemba]

Here is the proposed plan:

• [ ] Set up CHT 4.x docker, upload the PIH config and test to make sure nothing is broken.
• [ ] Update the PIH config and unit tests to align with the latest CHT version.
• [ ] Upgrade the PIH config to the target latest release.
• [ ] Test the config updates locally.
• [ ] Upload the updated PIH configs to this instance
• [ ] Review and complete the translations to align with the current demo app translations.
• [ ] Conduct and end to test workflows testing using the test-demo instance.
• [ ] Upload the updated PIH config to the demo instance
• [ ] Run an end to end testing of the workflows.
• [ ] Test the demo account creation process. Try to create a new user account and validate if the new user can access the updated CHT demo workflows, also verify if an already existing user can access the demo app.

[garethbowen]

@antonykhaemba Sounds good. We should also decide how we're going to maintain the new demo config going forward. Essentially it sounds like you're proposing forking the config because some of those changes won't be backwards compatible. I think this is the right approach so we can continue to evolve the demo config separately from the PIH config. Assuming this is the case, will it be committed directly to the cht-core repo, or a separate repo?

An alternative would be to publish it as a reference app as well, but that's probably out of scope for now.

[antonykhaemba]

Thanks @garethbowen for your feedback.

The PIH ref app is already published.

[garethbowen]

@antonykhaemba Yes but we will be making changes to it over time (eg: supporting 4.x) which will break backwards compatibility. Is that ok, or should we fork it as a separate demo app?

[antonykhaemba]

We can folk it as a separate demo app @garethbowen