iuno-tdm / juicemachineservice Goto Github PK

• How are machines being registered?
• How are machines authorized and authenticated?

The user should be warned, if he is trying to create a recipe that already exists.

Can only be done as sudo user and I'm none.

sudo mv /etc/nginx/sites-enabled/default /etc/nginx/sites-enabled/default.disabled

Only keep data the client needs to visualize the recipe list.

It's not clear where errors are handled and logged. Not all logs are readable and understandable. We have to look over all of them to get to a better solution.

Das "insert" auf die Patch Tabelle sollte innerhalb der Patch File erfolgen und nicht in PatchDBTool. Grund: Beim Starten der TDM Docker Image sollten die Patches automatische eingespielt werden

Implement a REST Route to retrieve recipes.
At first no database ist connected behind the rest route. So alle recipes retrieved are dummy-data

When a machine is beeing configured we need to know what ingredients are possible (known on the server). We need a REST Interface to retrieve a list of possible ingredients. The response JSON should represent the tree-like structure from the database spec.

Implement the Socket.IO Interface for machines to connect to. Socket.IO is used to push several information from the server to the client machines.

• Send offers and Payment Requests
• Send licence updats (RAU)

Recipe and user data also contain a URI to the user and recipe image. These URIs need to return those images.

Images are stored on the market place core. The JuiceMachineService should call the core for those images and return them to the client.

At a later point those thinks should also be cached.

After the latest discussions we do have a new understanding of the interface. The old specification does not match any longer.

The reports interfaces are not REST like and do need some refactoring.

• merge my_reports and reports.
• remove duplicated routes
• rename routes for better readability
• one route should have only one business logic

Implement a REST route so a client can place a order for a open offer.

From @bockha on March 28, 2018 6:43

The client id sent via socket.io to the juice machine service since IUNO-TDM/MixerControl@e1a51da must be securely checked for authenticity before being used.

Copied from original issue: IUNO-TDM/MixerControl#153

the socket.emit('room',topic) messages have to be resent after the connection to a socket.io server has been broken

The JuiceMachineService needs to be connected to the LicenceManager so the Service can push/trigger/retrieve updates for licences.

myreports-controller use the "includes" js function which is not supported on IE

Use the express.js framework to setup the basic structure.
Remove all view/frontend components as they will not be needed.

require a machine to authenticate itself using its cmdongle as identity provider, see also IUNO-TDM/MixerControl/issues/42

The authentication fails because the token is only reciecved once at startup.

• Fails if Auth Server is not reachable to this time
• Will fail as soon as the token expires

Implement a new route to create a offer request for a given recipe and amount.

Revise the RESTful interface definition interface.json so that it matches the implemented interface by 100%.

This is essential, since third parties shall be able to use this interface definition to generate code.

Application is now started within docker. We have to unstartup the old pm2 setup.

This can only be done as sudo user:

pm2 unstartup

// Do what every the cmd output tells you

We need a route to get user information from the server. This is used to show detail information about the recipe author on the machine frontend

The MachineService should not call the Core every time a client requests data. We should implement some caching functionality.

The Reports: MostUSedComponents, Technology per Day time and Revenue per Day time are not working.

Browser Error: Failed to load resource: the server responded with a status of 500 (Internal Server Error)

express-jsonschema

All json that is retrieved from the client via REST must be validated before processing it further.

Merge the two config files into a single one. Add some logic for private config files. Rethink the complete configuration process.

The ingredients should be named components or the other way. But we should stick on one naming to prevent missunderstandings.

Connect all routes to the market place core.

• Retrieve technology and other data from the core.
• Reformat the data to match the recipe interface