Microservice responsible for tracking activities, sleep, environments and measurements on the OCARIoT platform.
Main features:
- Tracking of physical activities;
- Tracking of sleep records;
- Tracking of environments;
- Tracking of measurements (weight and body fat).
See the documentation for more information.
Application settings are defined by environment variables.. To define the settings, make a copy of the .env.example
file, naming for .env
. After that, open and edit the settings as needed. The following environments variables are available:
VARIABLE | DESCRIPTION | DEFAULT |
---|---|---|
NODE_ENV |
Defines the environment in which the application runs. You can set: test (in this environment, the database defined in MONGODB_URI_TEST is used and the logs are disabled for better visualization of the test output), development (in this environment, all log levels are enabled) and production (in this environment, only the warning and error logs are enabled). |
development |
PORT_HTTP |
Port used to listen for HTTP requests. Any request received on this port is redirected to the HTTPS port. | 4000 |
PORT_HTTPS |
Port used to listen for HTTPS requests. Do not forget to provide the private key and the SSL/TLS certificate. See the topic generate certificates. | 4001 |
SSL_KEY_PATH |
SSL/TLS certificate private key. | .certs/server.key |
SSL_CERT_PATH |
SSL/TLS certificate. | .certs/server.crt |
RABBITMQ_URI |
URI containing the parameters for connection to the message channel RabbitMQ. The URI specifications defined by RabbitMQ are accepted. For example: amqp://user:pass@host:port |
amqp://guest:guest @127.0.0.1:5672 |
RABBITMQ_CA_PATH |
RabbitMQ CA file location. Must always be provided when using amqps protocol. |
.certs/rabbitmqca.crt |
MONGODB_URI |
Database connection URI used if the application is running in development or production environment. The URI specifications defined by MongoDB are accepted. For example: mongodb://user:pass@host:port/database?options |
mongodb://127.0.0.1:27017 /ocariot-iot-tracking |
MONGODB_URI_TEST |
Database connection URI used if the application is running in test environment. The URI specifications defined by MongoDB are accepted. For example: mongodb://user:pass@host:port/database?options |
mongodb://127.0.0.1:27017 /ocariot-iot-tracking-test |
For development and testing environments the easiest and fastest way is to generate your own self-signed certificates. These certificates can be used to encrypt data as well as certificates signed by a CA, but users will receive a warning that the certificate is not trusted for their computer or browser. Therefore, self-signed certificates should only be used in non-production environments, that is, development and testing environments. To do this, run the create-self-signed-certs.sh
script in the root of the repository.
./create-self-signed-certs.sh
The following files will be created: ca.crt
, server.crt
and server.key
.
In production environments its highly recommended to always use valid certificates and provided by a certificate authority (CA). A good option is Let's Encrypt which is a CA that provides free certificates. The service is provided by the Internet Security Research Group (ISRG). The process to obtain the certificate is extremely simple, as it is only required to provide a valid domain and prove control over it. With Let's Encrypt, you do this by using software that uses the ACME protocol, which typically runs on your host. If you prefer, you can use the service provided by the SSL For Free website and follow the walkthrough. The service is free because the certificates are provided by Let's Encrypt, and it makes the process of obtaining the certificates less painful.
npm install
Build the project. The build artifacts will be stored in the dist/
directory.
npm run build
npm start
Build the project and initialize the microservice. Useful for production/deployment.
npm run build && npm start
Run unit testing, integration and coverage by Mocha and Instanbul.
npm test
npm run test:unit
npm run test:integration
npm run test:cov
Navigate to the coverage
directory and open the index.html
file in the browser to see the result. Some statistics are also displayed in the terminal.
npm run build:doc
The html documentation will be generated in the /docs directory by typedoc.
In the Docker Hub, you can find the image of the most recent version of this repository. With this image it is easy to create your own containers.
docker run ocariot/iot-tracking
This command will download the latest image and create a container with the default settings.
You can also create the container by passing the settings that are desired by the environment variables. The supported settings are the same as those defined in "Set the environment variables". See the following example:
docker run -d --rm \
-e PORT_HTTP=4000 \
-e PORT_HTTPS=4001 \
-v $(pwd)/.certs:/etc \
-e SSL_KEY_PATH=/etc/server.key \
-e SSL_CERT_PATH=/etc/server.crt \
-e RABBITMQ_URI="amqp://guest:[email protected]:5672" \
-e MONGODB_URI="mongodb://127.0.0.1:27017/ocariot-iot-tracking" \
--name ocariot-iot-tracking \
ocariot/iot-tracking
If the MongoDB or RabbitMQ instance is in the host local, add the --net=host
statement when creating the container, this will cause the docker container to communicate with its local host.
docker run -d --rm \
--net=host \
...
To generate your own docker image, run the following command:
docker build -t image_name:tag .