I'd even prefer the solution @bakman2 and @Colin presented, by watching the file from within a flow and send it to that API. Nice and clean.
I don't see any reasonable need to modify the core code for this API call.
I'd even prefer the solution @bakman2 and @Colin presented, by watching the file from within a flow and send it to that API. Nice and clean.
I don't see any reasonable need to modify the core code for this API call.
so this flow is watching itself ? Fine until someone deletes that part of the flow.
If the end goal really is to do something multi-user (as per How to modify node-red deploy operation to save flow to database) then using the API is the correct way forward.
Unless the users are people you can afford to upset.
That watcher could run in a separate Node-RED instance solely for that purpose.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.