$ nvm use # uses node version in .nvmrc
$ yarn install
Build a production distributable DHIS2 zip file:
$ yarn build
Copy .env to .env.local and configure DHIS2 instance to use. Then start the development server:
$ yarn start
Now in your browser, go to http://localhost:8081.
$ yarn test
src/domain: Domain layer of the app (entities, use cases, repository definitions)src/data: Data of the app (repository implementations)src/webapp/pages: Main React components.src/webapp/components: React components.src/utils: Misc utilities.i18n/: Contains literal translations (gettext format)public/: General non-React webapp resources.
Future.ts: Async values, similar to promises, but cancellables and with type-safe errors.Collection.ts: Similar to Lodash, provides a wrapper over JS arrays.Obj.ts: Similar to Lodash, provides a wrapper over JS objects.HashMap.ts: Similar to ES6 map, but immutable.Struct.ts: Base class for typical classes with attributes. Features: create, update.Either.ts: Either a success value or an error.
We use TypeDoc:
$ yarn generate-docs
Update i18n .po files from i18n.t(...) calls in the source code:
$ yarn localize
Check the example script, entry "script-example"in package.json->scripts and src/scripts/example.ts.
The hook .husky/pre-push will scan the committed files with Trivy before pushing them.
The scan rules are defined at trivy-secret.yaml, there you can add rules to match or ignore strings. The default rule is to check that VITE_DHIS2_AUTH is not leaked. This means that a value that is not "admin:district" or 'admin:district' will trigger the leak scan.
Please note that markdown files are not scanned as they may contain examples of how to use the .env files.
If Trivy is not installed the scan can be skipped with a (y/N) prompt.
If the scan is having some issue or needs to be skipped for some reason use SKIP_SECRET_SCAN=1 git push.
The rationale of these skips is to avoid blocking work. Please, make sure that no secrets were added before using them.
In any case there is a GitHub action to perform a scan of the pushed content, but it can't prevent leaks, just allows to mitigate them faster.
-
Requests to DHIS2 will be transparently proxied (see
vite.config.ts->server.proxy) fromhttp://localhost:8081/dhis2/xyzto${VITE_DHIS2_BASE_URL}/xyz. This prevents CORS and cross-domain problems. -
You can use
.envvariables within the React app:const value = import.meta.env.NAME;