从节点红色内部使用REST的节点红色重新部署流程 [英] node-red redeploy flow using REST from within node-red

问题描述

我在bluemix中有一个节点红色流，它也使用dash-db节点.因此，每次执行某些数据库维护或其他原因时，此数据库连接都会丢失，并且所有写入操作都会失败.当我重新部署时，一切都很好.Bluemix仅显示最近几个小时的日志，因此我发现很难调试.同时，我正在考虑在检测到此问题后进行自动重新部署，以避免丢失写入.可以在同一节点红色应用程序本身中使用GET/flows和POST/flows来完成此操作吗?

I have a node-red flow in bluemix that uses dash-db nodes also. So each time some dash db maintenance or some other reason, this db connection gets lost and all writes fail. When i redeploy, everything is fine again. Bluemix shows only logs of last few hours hence I am finding it very difficult to debug. Meanwhile i was thinking of doing an automatic redeploy after i detect this issue to avoid losing writes. Can this be done using GET /flows followed by POST /flows in the same node-red app itself?

推荐答案

1. 作为dash-db节点的一个问题值得提出，因此作者可以帮助解决-是的，您可以回发流程.完整的admin http api记录在这里: http://nodered.org/docs/api/admin/-看一下/flows 上的"reload"选项.

   Yes, you can post back the flows. The full admin http api is documented here: http://nodered.org/docs/api/admin/ - have a look at the 'reload' option on /flows.

   这篇关于从节点红色内部使用REST的节点红色重新部署流程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！