How to run a node-red flow client side?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am trying to setup a webpage using particle.io's node-red service and would like to allow for multiple simultaneous users to customize their view without it affecting what is displayed to other users. My current setup is all anonymous users (no actual login).
Currently, if I setup a flow to load a detailed view of a sensor, whenever a user decides to view the data from a different device the display changes for everyone as everything is in a single server side instance.
Is there a way to tell node-red to run this detailed instance client side, and rather just stream a portion of the data from the server to the client?
node-red particle.io
add a comment |
I am trying to setup a webpage using particle.io's node-red service and would like to allow for multiple simultaneous users to customize their view without it affecting what is displayed to other users. My current setup is all anonymous users (no actual login).
Currently, if I setup a flow to load a detailed view of a sensor, whenever a user decides to view the data from a different device the display changes for everyone as everything is in a single server side instance.
Is there a way to tell node-red to run this detailed instance client side, and rather just stream a portion of the data from the server to the client?
node-red particle.io
add a comment |
I am trying to setup a webpage using particle.io's node-red service and would like to allow for multiple simultaneous users to customize their view without it affecting what is displayed to other users. My current setup is all anonymous users (no actual login).
Currently, if I setup a flow to load a detailed view of a sensor, whenever a user decides to view the data from a different device the display changes for everyone as everything is in a single server side instance.
Is there a way to tell node-red to run this detailed instance client side, and rather just stream a portion of the data from the server to the client?
node-red particle.io
I am trying to setup a webpage using particle.io's node-red service and would like to allow for multiple simultaneous users to customize their view without it affecting what is displayed to other users. My current setup is all anonymous users (no actual login).
Currently, if I setup a flow to load a detailed view of a sensor, whenever a user decides to view the data from a different device the display changes for everyone as everything is in a single server side instance.
Is there a way to tell node-red to run this detailed instance client side, and rather just stream a portion of the data from the server to the client?
node-red particle.io
node-red particle.io
asked Nov 27 '18 at 1:54
Aaron CovrigAaron Covrig
33
33
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No*
The only part of Node-RED that runs in the clients browser is the flow editor, all the actual processing runs in the backend. Also Node-RED only runs one flow at a time, if you want to run multiple independent flows (one per user) then they will each need a separate instance.
This sort of setup is possible but requires building a surrounding infrastructure (e.g. Sensetecnic's FRED platform) to manage the instances and you are most likely going to need to have actual users so you can connect a returning user back to their instance when they return.
* a long LONG time ago there was a port of Node-RED that ran entirely in the browser, no back end at all. But I have not heard of it in a long time and it only worked with a small subset of specially adapted nodes. I have not heard about it in a LONG time so I assume it is VERY out of date.
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53491660%2fhow-to-run-a-node-red-flow-client-side%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No*
The only part of Node-RED that runs in the clients browser is the flow editor, all the actual processing runs in the backend. Also Node-RED only runs one flow at a time, if you want to run multiple independent flows (one per user) then they will each need a separate instance.
This sort of setup is possible but requires building a surrounding infrastructure (e.g. Sensetecnic's FRED platform) to manage the instances and you are most likely going to need to have actual users so you can connect a returning user back to their instance when they return.
* a long LONG time ago there was a port of Node-RED that ran entirely in the browser, no back end at all. But I have not heard of it in a long time and it only worked with a small subset of specially adapted nodes. I have not heard about it in a LONG time so I assume it is VERY out of date.
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
add a comment |
No*
The only part of Node-RED that runs in the clients browser is the flow editor, all the actual processing runs in the backend. Also Node-RED only runs one flow at a time, if you want to run multiple independent flows (one per user) then they will each need a separate instance.
This sort of setup is possible but requires building a surrounding infrastructure (e.g. Sensetecnic's FRED platform) to manage the instances and you are most likely going to need to have actual users so you can connect a returning user back to their instance when they return.
* a long LONG time ago there was a port of Node-RED that ran entirely in the browser, no back end at all. But I have not heard of it in a long time and it only worked with a small subset of specially adapted nodes. I have not heard about it in a LONG time so I assume it is VERY out of date.
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
add a comment |
No*
The only part of Node-RED that runs in the clients browser is the flow editor, all the actual processing runs in the backend. Also Node-RED only runs one flow at a time, if you want to run multiple independent flows (one per user) then they will each need a separate instance.
This sort of setup is possible but requires building a surrounding infrastructure (e.g. Sensetecnic's FRED platform) to manage the instances and you are most likely going to need to have actual users so you can connect a returning user back to their instance when they return.
* a long LONG time ago there was a port of Node-RED that ran entirely in the browser, no back end at all. But I have not heard of it in a long time and it only worked with a small subset of specially adapted nodes. I have not heard about it in a LONG time so I assume it is VERY out of date.
No*
The only part of Node-RED that runs in the clients browser is the flow editor, all the actual processing runs in the backend. Also Node-RED only runs one flow at a time, if you want to run multiple independent flows (one per user) then they will each need a separate instance.
This sort of setup is possible but requires building a surrounding infrastructure (e.g. Sensetecnic's FRED platform) to manage the instances and you are most likely going to need to have actual users so you can connect a returning user back to their instance when they return.
* a long LONG time ago there was a port of Node-RED that ran entirely in the browser, no back end at all. But I have not heard of it in a long time and it only worked with a small subset of specially adapted nodes. I have not heard about it in a LONG time so I assume it is VERY out of date.
answered Nov 27 '18 at 9:02
hardillbhardillb
25.5k73463
25.5k73463
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
add a comment |
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
Thanks, that would be my luck; at least now I won't waste my time trying to do the impossible.
– Aaron Covrig
Nov 27 '18 at 11:02
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53491660%2fhow-to-run-a-node-red-flow-client-side%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown