You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the HyperStream container is executing unit tests on startup. We probably need to do something more clever here, for example one of Miquel's tutorials.
The text was updated successfully, but these errors were encountered:
I am still missing the final use of the HyperStream container. I would understand its use if it started a HyperStream server with the MongoDB and MQTT, everything in its own open ports. And then, a smaller version of an HyperStream client could connect to the server using the designed port. But at this moment, I am not sure about its real use case scenario.
@tdiethe did you think about the idea of HyperStream server-client approach?
About the tutorial container
I see that the tutorial one can be useful for somebody to start running the tutorials and understand how it works. But as it is in a Docker container, it makes difficult to understand everything that is going underneath and it is difficult to modify the configuration files, plugins, and extend the tutorials.
Because it can do something on its own it just runs the tests.
It's also kind of an example of how you can install hyperstream by looking at the dockerfile.
Re. the tutorials container. There is a way to plug in a local directory as a hyperstream-tutorials source i.e.:
you clone the hyperstream directory to your local machine
you run the containers and ask it to run the hyperstream from your local directory
you are free to modify whatever you like but you don't need any dependancies because everything is run in the docker container
At the moment the HyperStream container is executing unit tests on startup. We probably need to do something more clever here, for example one of Miquel's tutorials.
The text was updated successfully, but these errors were encountered: