tiefpunkt’s avatartiefpunkt’s Twitter Archive—№ 14,342

  1. Side note: Version control and Node-Red don't really mix well. The "Projects" feature kinda sucks, as it would require me to setup a dedicated Node-Red installation for each "project" if I want to run multiple at the same time. That totally kills all benefits of #nodered for me.
    On twitter.com Twitter logo tiefpunkt’s avatar ❤️ 1 Favorite Mood -1 🙁
    1. …in reply to @tiefpunkt
      Man, JavaScript isn't my thing really... But tried my best to take a first step to make this projects thing work better for me by splitting the #nodered flows file by tabs using a custom storage module: github.com/tiefpunkt/node-red-splitstorage If you have input on this: discourse.nodered.org/t/project-json-flow-separate-file-per-flow-tab/9409
      Permalink On twitter.com Twitter logo tiefpunkt’s avatar Mood +5 🙂
    2. …in reply to @tiefpunkt
      @knolleary are there any plans to push the "projects" thing any further? E.g. a project could be just one flow, or 2 or three, instead of all flows being one. So I could run different projects in different flows, and version them all separately (or some not at all even).
      Permalink On twitter.com Twitter logo tiefpunkt’s avatar Mood 0