https://github.com/reliefapplications/ems-backend
https://github.com/reliefapplications/ems-backend
ui-builder
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/reliefapplications/ems-backend
- Owner: ReliefApplications
- License: gpl-3.0
- Created: 2021-01-22T10:12:28.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2026-05-08T14:21:55.000Z (about 2 months ago)
- Last Synced: 2026-05-08T16:33:54.593Z (about 2 months ago)
- Topics: ui-builder
- Language: TypeScript
- Homepage:
- Size: 9.08 MB
- Stars: 38
- Watchers: 1
- Forks: 3
- Open Issues: 27
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
OORT Back-end
=======
[](https://img.shields.io/github/v/release/ReliefApplications/ems-backend)
[](https://github.com/ReliefApplications/ems-backend/actions/workflows/codeql-analysis.yml)
# Introduction
This back-end uses [Node.js](https://nodejs.org) and runs an [Express server](https://expressjs.com). The app data is stored in a [MongoDB](https://www.mongodb.com) database. It exposes a [GraphQL](https://graphql.org/) API.
It was made for a Proof of Concept of a UI Builder for WHO.
To read more about the project, and how to setup the back-end, please refer to the [documentation of the project](https://gitlab.com/who-ems/ui-doc).
* [Setup](https://gitlab.com/who-ems/ui-doc#how-to-setup)
* [Deployment](https://gitlab.com/who-ems/ui-doc#how-to-deploy)
# Utilities
Docker-compose executes nodemon command, which provides an inspector tool.
9229 port is allocated to back-end inspection. You can use inspector with browser tools.
For Chrome, go to **chrome://inspect)** and click on *inspect* below the remote target.
## Testing
In order to execute tests locally, you can execute the command:
```
docker-compose -f docker-compose.test.yml run test-server npm run test
```
Or this command:
```
npm run test
```
It is also possible to run tests on a single file, by passing it as a parameter:
```
docker-compose -f docker-compose.test.yml run test-server npm run test --
```
Or with this command:
```
npm run test --
```
You can also limit the tests to one specific folder. For example:
```
npm run test -- --testPathPattern=models
```
Note: If you're running the tests on Windows, make sure the test command in your `package.json` file is set up correctly. Here's the command that should be in the `scripts` section of your `package.json` file:
```json
"test": "node --max-old-space-size=8192 ./node_modules/jest/bin/jest.js --logHeapUsage --forceExit"
```
Will only run tests in the **models** folder.
# RabbitMQ
If management platform is not reachable at 15672, you can use this command ( while containers are running ):
```
docker-compose exec rabbitmq rabbitmq-plugins enable rabbitmq_management
```