TIP’s E-Heza Data Solutions is a digital app designed by and for the frontline health worker that can be used on a smartphone or tablet. E-Heza captures essential data at the point of care to improve the health of mother and child by providing frontline health workers with immediate insights to help personalize information and advice, and help the mother track the well-being of her child.
E-Heza has been added to the Digital Public Goods Alliance DPG Registry. The goal of the DPGA and its registry is to promote digital public goods in order to create a more equitable world. Being recognised as a DPG increases the visibility, support for, and prominence of open projects that have the potential to tackle global challenges. To become a digital public good, all projects are required to meet the DPG Standard to ensure that projects truly encapsulate open source principles.
The project is integrated with GitPod.
Click on the badge above to try it out the project in action and start editing
the source code! By default, Drupal and Elm client is accessible publicly, and you
can access other DDEV services like Mailhog using the non-HTTPS port, for instance
8026-
should work for checking the outgoing mails.
Primary ports:
8888
for Drupal3000
for Elm frontendadmin
/ admin
into the Drupal backend.12345678
as the pairing code (tied to Device nodes at the Drupal side).1234
as the PIN code (tied to the Nurse nodes at the Drupal side).elm make
might get killed by the OOM killer.cp .ddev/config.local.yaml.example .ddev/config.local.yaml
. Note that by default, installation is performed for Rwanda site. If you wish to install for Burundi site, set EHEZA_SITE=burundi
at .ddev/local.config.yaml
.cp client/src/elm/LocalConfig.Example.elm client/src/elm/LocalConfig.elm
module LocalConfig.Example exposing (localConfigs)
to module LocalConfig exposing (localConfigs)
ddev gulp
12345678
as the pairing code (tied to Device nodes at the Drupal side).1234
as the PIN code (tied to the Nurse nodes at the Drupal side).Make sure the following is installed:
npm install -g elm-format@0.8.1
), not strictly required for the development, but the standard must be followed, as Travis checks that. Therefore it's highly suggested to run Elm Format upon save at your IDE (https://github.com/avh4/elm-format#editor-integration).cp src/elm/LocalConfig.Example.elm src/elm/LocalConfig.elm
module LocalConfig.Example exposing (localConfigs)
to module LocalConfig exposing (localConfigs)
You may need to update src/elm/LocalConfig.elm
if your local URLs are different from the default setting.
ddev gulp
ddev gulp publish
gh-pages
branch of your repository): ddev gulp deploy
Frontend: http://localhost:3000 (that comes from inside DDEV after ddev gulp
)
The Drupal migration creates Devices, Nurses out of the box, so you can
12345678
as the pairing code (tied to Device nodes at the Drupal side).1234
as the PIN code (tied to the Nurse nodes at the Drupal side).If you have a dump from another source, to be able to work locally, first of all, you need to create a Device and a Nurse.
ddev drush uli
to login as admin
Our gulpfile.js
has a task ddev gulp zscore
which converts the raw Z-Score tables we
downloaded from the WHO web site into three formats:
This should all happen automatically when you run ddev gulp
.
After you edited an Elm file, and the compilation process is executed, the changes are not visible in the browser. To activate the new version you've just created, click on the "Version" indication in the top-right corner of the app. That will take you to a page which allows you to check for updates and activate updates.
The default method assumes Pantheon as the hosting service provider.
Prepare Config.Deploy.elm
based on Config.elm
that holds the
infrastructure-related data for Elm. This file is gitignored, and it is
used during Elm compilation, before the final artifact is pushed to Pantheon.
Put it in a private repository, and link that repository using
EHEZA_INFRA_REPO_REMOTE
, defined in .ddev/config.local.yaml.example
.
Also, set EHEZA_SITE
, to indicate the site installation is done for.
The repository does not have a strict structure, but the file should be
present at the elm/[EHEZA_SITE]/Config.Deploy.elm
path.
To propagate a new release, you can do the following:
ddev start
ddev auth ssh
ddev gulp publish
ddev robo deploy:pantheon
To generate the release notes, use ddev robo generate:release-notes prev-tag
.
When the site is initially installed in an environment, there are recurring jobs that need to be configured.
There are two main alternatives to achieve this. Either the hosting platform
provides customizable cron-jobs or we can invoke it from an external place,
like a Jenkins server.
Check the scripts in infrastructure_setup
directory, create either a Jenkins
job from those or you can invoke them via cron
or
supervisord
, edit the Bash variables at the
top of the scripts and study the file head comment that contains more
information of the dependencies of the scripts.
Example crontabs:
*/5 * * * * /path/to/app/infrastructure_setup/advancedqueue.sh
1 1 * * * /path/to/app/infrastructure_setup/reporting.sh
We recommend an external source, like Jenkins to trigger these, it's a comfortable, high-level tool with easily configurable logging / history. Inside Jenkins, these scripts can be "Freestyle project"s with "Build periodically" trigger and a "Shell" build part.
If that's a no-go, for the advancedqueue, supervisord
is a better choice,
as that queue needs to be processed all the time. For the reporting, a simple
cron job might be sufficient.