Nightscout Reporter

A web app based on Angular to create PDF documents from nightscout data.

It uses the api from cgm-remote-monitor to access the nightscout data and creates PDFs for handing out to diabetes doctors or coaches.

This is the transfer from Dart to Angular which was neccessary, since Dart is no longer maintained by the creators and the community-version of dart is not good enough with handling the dependencies of the framework. Hopefully Angular support will last longer than that of Dart.

Online version available at: https://nightrep.zreptil.de/
Compiled project avaialbe at: https://nightrep.zreptil.de/nightscout-reporter_local.zip

Getting started

Initial steps to compile, deploy, and run nightscout reporter on your own infrastructure.

Preparation

• Download or git clone the repository
• Download and install node.js from https://nodejs.org
• Install Angular using "npm install -g @angular/cli"

Build

• Call build.bat from the repository folder in cmd
• Result will be avaialbe in directory .\dist\nightrep

Deploy

• Get a web server (or online web space)
• Copy content of .\dist\nightrep to the content folder of your web server (or any subfolder)

You can run your own nightscout-reporter instance by calling the URL of your web-server in a browser.

IIS Hosting

Web.config

A web.config file is provided in the root-directory of the deployment.

Internationalization

(i18n is short for i-nternationalizatio-n - i followed by 18 letters and the letter n)

Every text in nightscout reporter can be translated. For this purpose Angular Internationalization is used: https://angular.io/guide/i18n-overview. The source language for nightscout reporter is german. I decided this, since this is my mother tongue and creating the program needed focus on the programming and not on the translation. So the first source of the translation is german. The translation itself takes place in https://crowdin.com/ and is mainly done by the community. I (zreptil) provide german and english as source for translations. The process of creating the translation follows these steps:

1. Extract all texts from code
2. Upload the created file with german language to crowdin

• Translate all texts from german to the given target languages
• Download the files for the target languages

3. Create the target language file for english as a source language file
4. Upload the created file with english language to crowdin

• Translate all texts from english to the given target languages
• Download the files for the target languages

5. Create the file assets/messages.json for use in the application

As you can see, the process is extensive and has some specialities since I decided to use german as source language. To make this tasks easier and reduce the source for problems, I created some helper-programs to go through the tasks. The tasks can be executed by going through the package.json and run the commands that start with "i18n-" and the number in the list above.

This works on a windows installation. I think the scripts have to be changed, when running in another environment. But since I am the only one who can upload the files to this crowdin projects and do the management of the languages there, I wrote this only to have a documentation of the concept. Everyone is invited to adapt this for his own purposes, but I cannot provide support for systems I do not run by myself.