-
Right now have to use the programmatic API,
or `noflo-runtime-msgflo --option=inports.in.queue=foo`
Using port metadata, would allow it to be visualized and edited in Flowhub, and be less verbose set…
-
This will make it show up nicely in Flowhub.
-
Given that @jonnor has successfully driven a JavaFBP network from a JSON network definition - which, in turn, can be generated from flowhub, it seems to me that flowhub will need a few more features …
-
-
Happens at least on Travis CI. For example: https://travis-ci.org/flowhub/the-graph/builds/454191240
Because of this they are currently disabled in Grunt.
-
Every time I start `noflo-nodejs`, the runtime has different ip address for ws listening, while the old address is kept saved in the indexed db at flowhub. This causes connection time out, and the onl…
-
```
INFO flowd_rs > got a client
INFO flowd_rs > entering receive loop
INFO flowd_rs > waiting for next message
INFO flowd_rs > got a text|binary message
INFO flowd_rs > got runtime:getr…
-
[Flowtrace](https://github.com/flowbased/flowtrace) allows tracing FBP programs for retroactive debugging. It has a `flowtrace-replay` commandline tool, which replays the data as if it was a 'live' FB…
-
Right now one can edit graphs, components, and (fbp-)spec files.
However, very often in a non-trivial project components import some non-component code. Sometimes the majority of the logic is done the…
-
For instance to broadcast the Flowhub live-url to connect to the system. Probably using their mDNS support, as `msgflo` broker typically runs on Linux which can have Avahi etc.