mirror of
https://github.com/node-red/node-red.git
synced 2023-10-10 13:36:53 +02:00
Updated Design: Runtime extension points (markdown)
parent
b8071e1814
commit
21ce69517a
@ -24,6 +24,10 @@ The requirements are:
|
|||||||
- perform some processing on the flows as part of the deploy process
|
- perform some processing on the flows as part of the deploy process
|
||||||
- be able to route messages between the instances are defined by the flow
|
- be able to route messages between the instances are defined by the flow
|
||||||
|
|
||||||
|
### Running different flows for different users
|
||||||
|
|
||||||
|
This is the case where different users have access to different node red instances/run times on a single multi-core server or cluster. To do this may require a suitable UI to manage users and instances, a way to broker communications to instances for administration (flow deployment, debugging) and access to flow inputs (e.g. HTTP, web sockets, others) based on user identity and credentials.
|
||||||
|
|
||||||
## Extension Points
|
## Extension Points
|
||||||
|
|
||||||
- Storage layer - how/where things get stored - [already done](http://nodered.org/docs/api/storage/index.html).
|
- Storage layer - how/where things get stored - [already done](http://nodered.org/docs/api/storage/index.html).
|
||||||
|
Loading…
Reference in New Issue
Block a user